Also find me on sh.itjust.works and Lemmy.world!

https://sh.itjust.works/u/lka1988
https://lemmy.world/u/lka1988

  • 0 Posts
  • 44 Comments
Joined 5 months ago
cake
Cake day: November 18th, 2024

help-circle


  • 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.



  • 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: I can 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, and Dockge will automatically see the compose file and the stack status. Or, I can point Dockge at a custom location such as /home/username/docker_stacks/, and so long as each compose file has a labeled folder inside that directory, that’s all you need to do to be done with it.

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









  • 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.






  • 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, and a couple others I can’t remember as it’s not here in front of me).

    I put a solid 7 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.