starred/uptime-kuma

Fork 0

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

Is Docker volume create and use as external volume in docker-compose to persist data is supported #2141

New issue

Closed

opened 2026-02-28 02:44:20 -05:00 by deekerman · 3 comments

deekerman commented

2026-02-28 02:44:20 -05:00

Owner

Originally created by @vairakkumaar-svs-hf on GitHub (Apr 25, 2023).

⚠️ Please verify that this bug has NOT been raised before.

I checked and didn't find similar issue

🛡️ Security Policy

I agree to have read this project Security Policy

📝 Describe your problem

Readme states: ' Please use a local volume only. Other types such as NFS are not supported."

Is external volume to persist data supported, this will allow to down uptime-kuma and bring it back up. If not what is the best method to persist data.

Simple docker-compose.yml

You can change your port or volume location

version: '3.3'

services:
uptime-kuma:
image: louislam/uptime-kuma:1
container_name: uptime-kuma
volumes:
- uptime-kuma-data:/app/data
ports:
- 3001:3001 # :
restart: always

volumes:
uptime-kuma-data:
external: true
name: uptime-kuma-data

📝 Error Message(s) or Log

no error message

🐻 Uptime-Kuma Version

1.21.2

💻 Operating System and Arch

ubuntu 20.04

🌐 Browser

112.0.5615.137 (Official Build) (64-bit)

🐋 Docker Version

Docker version 20.10.14, build a224086

🟩 NodeJS Version

No response

Originally created by @vairakkumaar-svs-hf on GitHub (Apr 25, 2023). ### ⚠️ Please verify that this bug has NOT been raised before. - [X] I checked and didn't find similar issue ### 🛡️ Security Policy - [X] I agree to have read this project [Security Policy](https://github.com/louislam/uptime-kuma/security/policy) ### 📝 Describe your problem Readme states: ' Please use a local volume only. Other types such as NFS are not supported." Is external volume to persist data supported, this will allow to down uptime-kuma and bring it back up. If not what is the best method to persist data. ` # Simple docker-compose.yml # You can change your port or volume location version: '3.3' services: uptime-kuma: image: louislam/uptime-kuma:1 container_name: uptime-kuma volumes: - uptime-kuma-data:/app/data ports: - 3001:3001 # <Host Port>:<Container Port> restart: always volumes: uptime-kuma-data: external: true name: uptime-kuma-data ` ### 📝 Error Message(s) or Log no error message ### 🐻 Uptime-Kuma Version 1.21.2 ### 💻 Operating System and Arch ubuntu 20.04 ### 🌐 Browser 112.0.5615.137 (Official Build) (64-bit) ### 🐋 Docker Version Docker version 20.10.14, build a224086 ### 🟩 NodeJS Version _No response_

deekerman

2026-02-28 02:44:20 -05:00

closed this issue
added the
Stale

help
labels

deekerman commented

2026-02-28 02:44:25 -05:00

Author

Owner

@louislam commented on GitHub (Apr 26, 2023):

Yes, it is persistent. The message means that you should not use a network drive as the volume.

@louislam commented on GitHub (Apr 26, 2023): Yes, it is persistent. The message means that you should not use a network drive as the volume.

deekerman commented

2026-02-28 02:44:25 -05:00

Author

Owner

@github-actions[bot] commented on GitHub (Jul 25, 2023):

We are clearing up our old issues and your ticket has been open for 3 months with no activity. Remove stale label or comment or this will be closed in 2 days.

@github-actions[bot] commented on GitHub (Jul 25, 2023): We are clearing up our old issues and your ticket has been open for 3 months with no activity. Remove stale label or comment or this will be closed in 2 days.

deekerman commented

2026-02-28 02:44:25 -05:00

Author

Owner

@github-actions[bot] commented on GitHub (Jul 27, 2023):

This issue was closed because it has been stalled for 2 days with no activity.

@github-actions[bot] commented on GitHub (Jul 27, 2023): This issue was closed because it has been stalled for 2 days with no activity.

deekerman referenced this issue

2026-02-28 03:02:48 -05:00

[Bug] Cannot read properties of null (reading '_dockerType') #2665