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.

You’re not wrong; I was just being hyperbolic.

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.

An immutable distro would be ideal for this kind of thing. ChromeOS (an immutable distro example) can be centrally managed, but the caveat with ChromeOS in particular is that it’s management can only go through Google via their enterprise Google Workspace suite.

But as a concept, this shows that it’s doable.

TL;DR - Because people are stupid.

One of my coworkers (older guy) tends to click on things without thinking. He’s been through multiple cyber security training courses, and has even been written up for opening multiple obvious phishing emails.

People like that are why company-owned laptops are locked down with group policy and other security measures.

Systemd is fine. This sounds like an old sysadmin who refuses to learn because “new thing bad” with zero logic to back it up.

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.

Cinnamon by and far.

I’ve used so many distros and DEs I don’t even know where to begin, but Cinnamon got me hooked for the long run. It’s legitimately the most polished and “ready to run” DE I’ve ever used, yet still allowing for far more customization than Windows ever offered.

That thread was a godsend. Turning off tcpkeepalive was the other one that I couldn’t remember, but that seemed to help out as well.

My wife has had multiple MacBooks over the years (I set up her old 2009-era A1278 with Linux Mint for the kids to do homework), and after I “fixed” it and talked about the longer wake-up process, she told me that’s what she was used to already and the “super fast wake up” was a very new thing for her when she bought it. So no complaints from her, and the battery performs better. Win/win.

My Thinkpad T14 running Linux Mint (LMDE) gets better battery life on “Suspend” than that damn MBP does when hibernated. It’s the 2017 A1706, too - out of ALL the variants it had to be that one 😂

I mean, this is about privacy, is it not? It’s pretty well-known by now that Windows mines your data.

It depends how much shit is blocked on the network at the user level.

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.

So here’s the thing - if you can think of it, I’ve already tried it 😅 I spent a week and a half sifting through countless forum posts on Apple’s own support center, Macrumors, reddit, and a host of other forums.

The “Wake for network access” setting was the first thing I disabled after I wiped and reinstalled the OS. Among a number of other settings, including “Power Nap”. Still got the fucking “EC.DarkPME (Maintenance)” process firing off every ~45 seconds, no matter what I did, causing excessive insomnia and draining the battery within 12 hours.

What I ended up doing was using a little tool called “FluTooth” to automatically disable wifi/Bluetooth on sleep (the built-in OS settings did fuck-all), set hibernationmode to 25, and a few other tweaks with pmset that currently escape me (edit: disabled networkoversleep, womp, ttyskeepawake, powernap - which was still set to 1 even with the setting in System Settings was disabled 🤨), and a couple others I can’t remember as it’s not here in front of me).

I put several full charge cycles on the brand new battery before it finally calmed the fuck down.

As someone who just had to bandaid an unexplained battery draw on his wife’s MacBook - no, Mac OS no longer “just works”. Apple buries some of the most basic settings inside a command line-only tool called pmset, and even then those can be arbitrarily overridden by other processes.

And even after a fresh reinstall and new battery, it still drains the battery faster in hibernation mode than my Thinkpad T14 G1 running LMDE does while sleeping. Yeah, that was a fun discovery.

That Thinkpad is by far one of my most dependable machines.

And did you verify this before posting?