DockGE released 1.5.0
-
For those unfamiliar, DockGE is "A fancy, easy-to-use and reactive self-hosted docker compose.yaml stack-oriented manager."
Similar to portainer
Warning
Breaking change: Due to the security reason, the "Console" feature is now disabled by default. If you need this feature and understand the risk, you can enable it via the environment variable DOCKGE_ENABLE_CONSOLE=true.
See link for full notes
-
System shared this topic on
-
For those unfamiliar, DockGE is "A fancy, easy-to-use and reactive self-hosted docker compose.yaml stack-oriented manager."
Similar to portainer
Warning
Breaking change: Due to the security reason, the "Console" feature is now disabled by default. If you need this feature and understand the risk, you can enable it via the environment variable DOCKGE_ENABLE_CONSOLE=true.
See link for full notes
I'm a fan of Dockge. Nice simplicity, easy to update container stacks, etc. etc.
-
For those unfamiliar, DockGE is "A fancy, easy-to-use and reactive self-hosted docker compose.yaml stack-oriented manager."
Similar to portainer
Warning
Breaking change: Due to the security reason, the "Console" feature is now disabled by default. If you need this feature and understand the risk, you can enable it via the environment variable DOCKGE_ENABLE_CONSOLE=true.
See link for full notes
I used this for a bit. Can you import existing stacks yet? That was my missing feature.
-
I used this for a bit. Can you import existing stacks yet? That was my missing feature.
If the compose.yml can be moved to a place where Dockge is configured to look, then yes. Normally it's configured to look in
/opt/stacks/, but that can be changed. -
If the compose.yml can be moved to a place where Dockge is configured to look, then yes. Normally it's configured to look in
/opt/stacks/, but that can be changed.I just updated my dockge container, you still have to start compose files from dockge in order to manage them. Which requires copy/pasting compose files into dockge. If you have more than 2-3 compose files, this is a pia. To me, that's not an import.
-
I just updated my dockge container, you still have to start compose files from dockge in order to manage them. Which requires copy/pasting compose files into dockge. If you have more than 2-3 compose files, this is a pia. To me, that's not an import.
Dockge doesn't really work like that. It works alongside Docker, the only thing it asks is that you point it to where your stacks are located. Like I said, that normally is set to
/opt/stacks/, but it's not set in stone. -
For those unfamiliar, DockGE is "A fancy, easy-to-use and reactive self-hosted docker compose.yaml stack-oriented manager."
Similar to portainer
Warning
Breaking change: Due to the security reason, the "Console" feature is now disabled by default. If you need this feature and understand the risk, you can enable it via the environment variable DOCKGE_ENABLE_CONSOLE=true.
See link for full notes
preserve YAML comments when reordering items
This fix is massive, lost a lot of useful info when I moved my yml files
-
Dockge doesn't really work like that. It works alongside Docker, the only thing it asks is that you point it to where your stacks are located. Like I said, that normally is set to
/opt/stacks/, but it's not set in stone.Thanks for the detailed explanation! One thing is unclear to me, though: what's the difference between the path and the why do I still need the ENV in addition? Won't they match anyway in 99% of the cases? Since there's not really a reason to not set the path to the stack folder?
-
Thanks for the detailed explanation! One thing is unclear to me, though: what's the difference between the path and the why do I still need the ENV in addition? Won't they match anyway in 99% of the cases? Since there's not really a reason to not set the path to the stack folder?
The env variable is within the compose file itself - it's fairly simple.
-
The env variable is within the compose file itself - it's fairly simple.
Yeah, I saw that, but why is it needed in the first place? Just in case the stack is in a subfolder of the path? But why even do that, if the ENV only accepts a single value anyway? I'm wondering in which cases the path differs from the DOCKGE_STACKS_DIR env var?
-
Yeah, I saw that, but why is it needed in the first place? Just in case the stack is in a subfolder of the path? But why even do that, if the ENV only accepts a single value anyway? I'm wondering in which cases the path differs from the DOCKGE_STACKS_DIR env var?
It's needed because that's how Dockge manages the compose files - it needs to know where your compose files live.
-
Dockge doesn't really work like that. It works alongside Docker, the only thing it asks is that you point it to where your stacks are located. Like I said, that normally is set to
/opt/stacks/, but it's not set in stone.Thanks for the info, that's definitely not how it's working on my system, so I have something setup wrong. That explains my confusion.
-
Thanks for the info, that's definitely not how it's working on my system, so I have something setup wrong. That explains my confusion.
Let us know if you run into more snags! I'm happy to try to help out. I also revised my comment above several times last night and this morning as I was really tired and kept forgetting details
The other thing to note is the "Scan Stacks Folder" option in the drop-down menu. I haven't really needed to use it as Dockge tends to find my compose files on its own, but it's worth mentioning.
-
preserve YAML comments when reordering items
This fix is massive, lost a lot of useful info when I moved my yml files
I haven't experienced this, oddly enough. Many of my compose files have comments, and they're still visible
-
I haven't experienced this, oddly enough. Many of my compose files have comments, and they're still visible
They get deleted when you edit the configuration using the webui
-
For those unfamiliar, DockGE is "A fancy, easy-to-use and reactive self-hosted docker compose.yaml stack-oriented manager."
Similar to portainer
Warning
Breaking change: Due to the security reason, the "Console" feature is now disabled by default. If you need this feature and understand the risk, you can enable it via the environment variable DOCKGE_ENABLE_CONSOLE=true.
See link for full notes
Breaking change: Due to the security reason, the "Console" feature is now disabled by default. If you need this feature and understand the risk, you can enable it via the environment variable DOCKGE_ENABLE_CONSOLE=true.
Good that they made a decision, the old security features restricting which commands you could run was awful and could be bypassed by accident.
-
I used this for a bit. Can you import existing stacks yet? That was my missing feature.
You don't need to, as long as our stack is all in one folder you just point it to that folder and it will work
-
The stack might be anywhere, mine has
DOCKGE_STACKS_DIR=/home/servicesbecause that's where I keep my stack. That's the only value, there aren't 2, so not sure what you meant in the other comment with "they match 99% of the time" -
System shared this topic on
