I haven’t experienced this, oddly enough. Many of my compose files have comments, and they’re still visible 🤔

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.

It’s needed because that’s how Dockge manages the compose files - it needs to know where your compose files live. Dockge normally lives in it’s own directory, /opt/dockge/ (the dev gave a reason for that, but I don’t remember why), so it won’t see anything else until you point it to wherever your compose files are normally located.

The env variable is within the compose file itself - it’s fairly simple.

I think you might be misunderstanding here, Dockge doesn’t really work like that. You don’t import “into” Dockge - it works alongside Docker, and all you need to do is point it to where your compose files are located. Which, like I said, is normally set to /opt/stacks/ - but that’s not set in stone and can be changed to another location via the DOCKGE_STACKS_DIR= env variable within Dockge’s own compose file (located in /opt/dockge/).

For example: Say I create the directory /opt/stacks/docker_container/, drop in my “docker_container” compose.yml file, and fire it up in the terminal with docker compose up -d, all via CLI without touching Dockge at all. Dockge will still automatically see the compose file and the stack status. Or, say I have a previously-established Docker host with all the compose files in a location such as /home/username/docker_stacks/, and I really don’t want to move them - so long as Dockge is configured to point at that directory, and the directory contains a labeled folder for each compose file (just like you would do normally), again, Dockge will automatically see the compose files and stack status. I’ve configured multiple hosts to use Dockge, and it’s really that simple.

Also, something I just remembered - the directory structure for your compose files, wherever it’s located, needs to be all lowercase. Otherwise Dockge won’t see it.

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’ve had the oil in my 2008 Sienna analyzed a few times by Blackstone Labs, and have been told that 5k miles is what I should stick to.

Why would you install a GUI on a VM designated to run a Docker instance?

You should take a serious look at what actual companies run. It’s typically nested VMs running k8s or similar. I run three nodes, with several VMs (each running Docker, or other services that require a VM) that I can migrate between nodes depending on my needs.

For example: One of my nodes needed a fan replaced. I migrated the VM and LXC containers it hosted to another node, then pulled it from the cluster to do the job. The service saw minimal downtime, kids/wife didn’t complain at all, and I could test it to make sure it was functioning properly before reinstalling it into the cluster and migrating things back at a more convenient time.

Those have a decent aftermarket though. Spotify at least issued refunds, so there’s that.

Damn, that’s impressive. My rig idles at ~110W, but I’ve heard that the 5800X3D just…does that. Especially so with the fact that it has AMD’s beefiest GPU.

Slap a few zigbee smart plugs into your setup, cluster them in Home Assistant, and measure the total power draw. That’s what I do. It’s eye-opening… I learned that my 5800X3D/7900XTX gaming PC is capable of pulling exponentially more power than my entire server cluster. I shut that thing off when I’m not using it now haha.

Even first gen i-series Intel CPUs support VT-d. I had an i7-870 that ran my entire setup under Proxmox for several years, until early 2023.

What you really need is RAM. In my case, ~32GB per node in a three-machine cluster is not quite enough, but a 4c/8t CPU is more than plenty.

I run 3x 7th gen Intel mini PCs in a Proxmox cluster, plus a 2014 Mac mini on a 4th gen i5 attached to 3x 4TB drives in RAID5 (my NAS), plus an 8TB backup drive. I also run Home Assistant on a Lenovo M710q Tiny (separate because I use Zigbee and don’t wanna deal with USB passthrough and migrating VMs and containers…). Total average draw is ~100W.

I feel this. My work phone is an iPhone 12, and typing is a pain compared to Android.

I have a Steam Deck dock specifically for this. Except the mouse comes up on the phone screen instead of the monitor. Weird bug.

Make sure you utilize the 80% charge feature

I’ll have to give this a shot with pi-hole later tonight.

In all seriousness, I think a “mobile server” in laptop-like form would be pretty nice. Have a giant battery attached to the bottom and program the controller to run on AC as it’s primary power source while treating the battery as a secondary source. Definitely niche, but cool nonetheless.

Docker does work on Android. That’s what OP is showing off.