starred/uptime-kuma

Fork 0

mirror of https://github.com/louislam/uptime-kuma.git synced 2026-03-02 22:57:00 -05:00

[Enhancement] Add an example docker-compose.yml file to the docs #25

New issue

Closed

opened 2026-02-28 01:32:10 -05:00 by deekerman · 5 comments

deekerman commented

2026-02-28 01:32:10 -05:00

Owner

Originally created by @ColaIan on GitHub (Jul 12, 2021).

as title :D

Originally created by @ColaIan on GitHub (Jul 12, 2021). as title :D

deekerman

2026-02-28 01:32:10 -05:00

closed this issue
added the
A:documentation
label

deekerman commented

2026-02-28 01:32:14 -05:00

Author

Owner

@TheGuyDanish commented on GitHub (Jul 12, 2021):

Is that really necessary? Uptime-Kuma runs in a single container without any database dependencies. I don't see the reason to user docker-compose for a small application like this.

@TheGuyDanish commented on GitHub (Jul 12, 2021): Is that really necessary? Uptime-Kuma runs in a single container without any database dependencies. I don't see the reason to user docker-compose for a small application like this.

deekerman commented

2026-02-28 01:32:14 -05:00

Author

Owner

@ColaIan commented on GitHub (Jul 12, 2021):

Is that really necessary? Uptime-Kuma runs in a single container without any database dependencies. I don't see the reason to user docker-compose for a small application like this.

Hm 🤔I guess it might still be a good idea to have it as you would only need to run docker-compose up, which is more convenient than making a bash file with a docker run command, and imo docker-compose is easier to manage

@ColaIan commented on GitHub (Jul 12, 2021): > Is that really necessary? Uptime-Kuma runs in a single container without any database dependencies. I don't see the reason to user docker-compose for a small application like this. Hm 🤔I guess it might still be a good idea to have it as you would only need to run docker-compose up, which is more convenient than making a bash file with a docker run command, and imo docker-compose is easier to manage

deekerman commented

2026-02-28 01:32:14 -05:00

Author

Owner

@TheGuyDanish commented on GitHub (Jul 12, 2021):

Again, not sure why you'd really want to. The oneliner in the README is quite simple, but you can get the job done with:

version: "3.9"
services:
  app:
    image: louislam/uptime-kuma
    ports:
      - "3001:3001"
    volumes:
      - /opt/uptime-kuma:/app/data

@TheGuyDanish commented on GitHub (Jul 12, 2021): Again, not sure why you'd really want to. The oneliner in the README is quite simple, but you can get the job done with: ```yaml version: "3.9" services: app: image: louislam/uptime-kuma ports: - "3001:3001" volumes: - /opt/uptime-kuma:/app/data ```

deekerman commented

2026-02-28 01:32:14 -05:00

Author

Owner

@louislam commented on GitHub (Jul 19, 2021):

Added docker-compose.yml file in source code, but I think "docker run" is suitable for most users too.

@louislam commented on GitHub (Jul 19, 2021): Added docker-compose.yml file in source code, but I think "docker run" is suitable for most users too.

deekerman commented

2026-02-28 01:32:14 -05:00

Author

Owner

@TheColetrain commented on GitHub (Nov 20, 2021):

Again, not sure why you'd really want to. The oneliner in the README is quite simple, but you can get the job done with:
version: "3.9"
services:
  app:
    image: louislam/uptime-kuma
    ports:
      - "3001:3001"
    volumes:
      - /opt/uptime-kuma:/app/data

thank you! because I am noobish! Nice for portainer.

@TheColetrain commented on GitHub (Nov 20, 2021): > Again, not sure why you'd really want to. The oneliner in the README is quite simple, but you can get the job done with: > > ```yaml > version: "3.9" > services: > app: > image: louislam/uptime-kuma > ports: > - "3001:3001" > volumes: > - /opt/uptime-kuma:/app/data > ``` thank you! because I am noobish! Nice for portainer.

deekerman referenced this issue

2026-02-28 01:50:34 -05:00

Lost every config during update #558

deekerman referenced this issue

2026-02-28 03:01:34 -05:00

Looping Crash After Deleting Monitor #2627