Comments (14)
@AmIBeingObtuse Thanks your reply, can u try to add the belows compose.yaml
to check the uptime-kuma data
stored position?
version: "3.8"
services:
uptime-kuma:
image: louislam/uptime-kuma:1
container_name: uptime-kuma
volumes:
- ./data:/app/data
- /var/run/docker.sock:/var/run/docker.sock:ro
ports:
- 13001:3001 # <Host Port>:<Container Port>
restart: always
I also will try to use C:
to store all stacks and data at tonight
from dockge.
I agree @AmIBeingObtuse.
@louislam I think the compose.yaml and other documentation should be updated to reflect this.
from dockge.
No, using 1
is the best.
1
is pointing the latest version of v1
.
latest
is a bad practice for most images:
https://stackoverflow.com/questions/72889955/is-it-bad-practice-to-use-mysqllatest-as-docker-image
from dockge.
Yes, because of the path mapping issue on Windows, I would say currently Dockge's container is not supported on Windows.
I will add non-Docker method later for Windows.
from dockge.
Thanks for the reply.
from dockge.
Hi
I run Dockge on docker desktop on windows 10 pro. I don't have any issues with mapping. Here is my compose file and converted run command that I use:
version: "3.8"
services:
dockge:
image: louislam/dockge:latest
restart: unless-stopped
ports:
# Host Port:Container Port
- "5032:5001"
volumes:
- "/var/run/docker.sock:/var/run/docker.sock"
- "C:\Yourpath\Data:/app/data"
# If you want to use private registries, you need to share the auth file with Dockge:
# - /root/.docker:/root/.docker
# Your stacks directory in the host (The paths inside container must be the same as the host)
# ⚠️⚠️ If you did it wrong, your data could end up be written into a wrong path.
# ✔️✔️✔️✔️ CORRECT EXAMPLE: - /my-stacks:/my-stacks (Both paths match)
# ❌❌❌❌ WRONG EXAMPLE: - /docker:/my-stacks (Both paths do not match)
- "C:\Yourpath\Stacks:/opt/stacks"
environment:
# Tell Dockge where is your stacks directory
- `"DOCKGE_STACKS_DIR=/opt/stacks"`
Docker run command:
docker run -d `
--name dockge `
-p 5032:5001 `
--restart unless-stopped `
-v /var/run/docker.sock:/var/run/docker.sock `
-v C:\Yourpath\Data:/app/data `
-v C:\Yourpath\Stacks:/opt/stacks `
-e DOCKGE_STACKS_DIR=/opt/stacks `
louislam/dockge:latest
This stores my stacks in C:\Yourpath\Stacks\StackName\compose.yaml
Docker prompted me to confirm I was happy sharing the directory. If that doesn't happen for you, go into docker dekstop settings and resources to ensure the directory is listed as shared. I am also using hyper v not WSL.
Let me know if this helped. I'm assuming your using docker desktop on windows.
from dockge.
@AmIBeingObtuse Thanks your reply, can u try to add the belows
compose.yaml
to check theuptime-kuma data
stored position?version: "3.8" services: uptime-kuma: image: louislam/uptime-kuma:1 container_name: uptime-kuma volumes: - ./data:/app/data - /var/run/docker.sock:/var/run/docker.sock:ro ports: - 13001:3001 # <Host Port>:<Container Port> restart: alwaysI also will try to use
C:
to store all stacks and data at tonight
Because I have mapped my paths in my compose as:
- "C:\Yourpath\Stacks:/opt/stacks"
and left the environmental variable as:
- `"DOCKGE_STACKS_DIR=/opt/stacks"`
Your compose file gets stored in:
- "C:\Yourpath\Stacks\UptimeKuma\compose.yaml"
for me.
I had to change your compose file to:
version: "3.8"
services:
uptime-kuma:
image: louislam/uptime-kuma:1
container_name: uptime-kuma
volumes:
- C:\Yourpath\Uptimekuma:/app/data
- /var/run/docker.sock:/var/run/docker.sock:ro
ports:
- 13001:3001 # <Host Port>:<Container Port>
restart: always
So I can persist the data and make it easier to access the files. But it did work fine via Dockge.
from dockge.
C:\Yourpath\Uptimekuma:/app/data
Yes, you are right. As long as it is a absolute path, it is ok to use, but I assume that most people will not aware this, so I claimed that Dockge is not supported on Windows at the moment.
from dockge.
Surely its a standard mapping?
I don't think it needs any change at all. As long as the volume is mapped as shown it works fine. That doesn't mean its not windows supported.
Maybe just provide a note in the default compose file for example:
version: "3.8"
services:
dockge:
image: louislam/dockge:1
restart: unless-stopped
ports:
# Host Port : Container Port
- 5001:5001
volumes:
- /var/run/docker.sock:/var/run/docker.sock
- ./data:/app/data #Example On Windows you can map the volume as - C:\Yourpath\Dockge\Data:/app/data
# If you want to use private registries, you need to share the auth file with Dockge:
# - /root/.docker/:/root/.docker
# Your stacks directory in the host (The paths inside container must be the same as the host)
# ⚠️⚠️ If you did it wrong, your data could end up be written into a wrong path.
# ✔️✔️✔️✔️ CORRECT: - /my-stacks:/my-stacks (Both paths match)
# ❌❌❌❌ WRONG: - /docker:/my-stacks (Both paths do not match)
- /opt/stacks:/opt/stacks #Example on windows you can map the volume as - C:\Yourpath\Dockge\Stacks:/opt/stacks
environment:
# Tell Dockge where is your stacks directory (If using windows keep this the same and see above for volume mapping).
- DOCKGE_STACKS_DIR=/opt/stacks
IMO
from dockge.
I have a another question, if I used absolute path on dockge volumes
volumes:
- "/var/run/docker.sock:/var/run/docker.sock"
- "C:/Yourpath/Data:/app/data"
- "C:/Yourpath/Stacks:/opt/stacks"
environment:
- `"DOCKGE_STACKS_DIR=/opt/stacks"`
Need I use absolute path on all stacks volume which mapped data? e.g.
version: "3.8"
services:
uptime-kuma:
image: louislam/uptime-kuma:1
container_name: uptime-kuma
volumes:
- - ./data:/app/data
+ - C:/Yourpath/Uptimekuma:/app/data
- /var/run/docker.sock:/var/run/docker.sock:ro
ports:
- 13001:3001 # <Host Port>:<Container Port>
restart: always
If uptime-kuma
always need absolute path to bind mount /app/data
, may dockge volumes
use relative path instead of absolute path?
from dockge.
from dockge.
Should this:
image: louislam/dockge:1
be this?
image: louislam/dockge:latest
from dockge.
Should this:
image: louislam/dockge:1
be this?
image: louislam/dockge:latest
Yes should be latest.
This install video for Dockge on windows really helped me
https://youtu.be/lEwEgR-nja4?si=OyuGy_M_gWP-Ywww
from dockge.
No, using
1
is the best.
1
is pointing the latest version ofv1
.
latest
is a bad practice for most images:https://stackoverflow.com/questions/72889955/is-it-bad-practice-to-use-mysqllatest-as-docker-image
I can understand why using the version number as the tag is best practice. I guess I'm used to devs posting only the latest stable version on that latest tag and using nightly for the latest unstable version.
I do use version tags for databases always. But I do agree with you.
from dockge.
Related Issues (20)
- Can't paste text into the console HOT 1
- Update readme HOT 1
- paperless-ngx: running stack is shown as inactive HOT 10
- Unable to maximize docker compose editor HOT 1
- impossible to maximize each part of dockge HOT 1
- Unable to sort stacks by server/agent
- Allowed console commands can be easily bypassed HOT 5
- Lost connection to the socket server. Reconnecting... HOT 9
- String escape problem
- docker login does not work via GUI HOT 2
- Allow adding remote docker nodes for centralised management HOT 1
- arm64/V8
- cannot run HOT 1
- Connection to remote aggent with reverse proxy in front does not work HOT 4
- Feature: Auto start on request HOT 1
- docker compose 'version' is obsolete
- Improper docker run -> compose conversion for volumes
- This stack is not managed by Dockge HOT 1
- Automatic page refresh wipes all changes
- Compose Volume Failure on subpath HOT 3
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from dockge.