I’m relatively new to the Docker “scene” and this looks like a really cool and simple way to manage the containers. (Looks easier than Portainer which I think is more business orientated)

Not sure if I’m missing a feature though - I already have a folder “docker” with sub folders for each container. Each container sub-folder contains a docker-compose.yml file

Is dockge able to automatically scan, import and give the option to deploy these containers?

If so, how do I do that?

I have the dockge stacks folder to be my top-level “docker” folder

TIA

Great project, I love the idea. It would be even greater if you could manage images, like in Portainer for example (My use case: deleting unused images). The same question applies to the topic of volumes. Is it possible to integrate other Docker repositories as well? For Security reason it could be nice to use 2FA or Passkeys. :)

I will eagerly follow the development.

This is cute but I have to be honest I prefer using VS code with SSH and docker plugins for managing compose files.

Amazing!

I spun it up for a try. First impressions… goodbye Portainer.

Maybe.

Question: Once I’ve used dockge to create multiple containers the yaml is nicely organised as separate compose files in the subfolder. Is it possible to use docker compose command to recursively up -d them all at once from the shell without having to manually specify the file names? It doesn’t support wildcards afaik?

Looks great, unfortunately i’m running on docker swarm. Hope it’ll support that somewhere in the future so i can use it. As i’m a great fan of uptime kuma and use it for work and private.

I’m finally ‘really’ getting into Docker because of this easy-to-understand helper app.

Portainer, etc have too much going on and is wildly overkill for single instance hosts.

Basic image management/info would be a nice addition.

Great work!

As a big fan of UK, I am looking forward to try out Dockge! Thank you so much for your work and dedication to the selfhosted community.

What would be great is integration with github or other source code management system. Also if you do this would be great to track/show version that is running.

Docked in, and loaded up! Quickly renamed my old docker-compose.yml to compose.yaml with this script running in my ‘compose’ folder of folders.

Pure beauty!

Thank you for making something not overly configurable, and something that just works.

This is now my new manager over SSH’ing in over tailscale, and trying to find new SSH apps every other week for my iPhone/Mac.

Literally hours saved.

A feature that would be nice to have is default settings for compose files. If I want to map user permissions, or map my media folder that is always going to be on my *arrrrrrrrr containers, that would be suuuper legit.

I’m gonna poke through the source once I get time to myself and see what I can come up with.

The quality of your work is amazing, and I genuinely thank you for allowing me now to setup/manage my containers while sitting on the toilet.

looking good! Not sure if this is the direction you’re looking to go with this project, but I’d love to see a docker compose stack manager that integrated a simple snapshot / backup system. My current situation (with Portainer) when I kludge something up is to either hope I can reconfigure things back they way they were, or revert my entire VM to an earlier state. I’d love to be able to revert a single stack in a few clicks (extra love if the solution used ZFS :). Related features might be simple one-file backup of a stack, or ability to easily migrate a stack from one host to another.

Would this work with .env files too?

As a newb to docker and as someone who hasn’t fully gelled with it this looks perfect. Seems it is doing exactly what I’m trying to do in the command line with the folder structures. Perfect timing as yesterday I completely lost the plot with my docker installation!

Looks really good and I moved a few of the once I have into dockge. Works great. One suggestion. Add Down and Up buttons as well. Just stopping a container does not always work when you upgrade them. All depending on volumes and configuration of the stack