How do you keep up?
-
I am not the person to be asking, I am no docker expert. It's is my understanding depends_on: defines starting order. Once a service is started, it's started. If it has an internal check for "healthy" I believe watchtower will restart unhealthy containers.
This is blind leading the blind though, I would check the documentation if using watchtower. We should both go read the "depends on" documents as we both use it.
-
Strangely it sounds like that's correct. I was under the understanding that depends_on cared about it past start as well but it does not. It doesn't look like there's a native way of turning containers that are depending on one another when you turn the dependency off. It looks like the current recommended way of doing it is either with a Docker compose file (which doesn't help if the process crashed), or having a third party script on the host monitor is the dependencies and if one is considered offline, it turns the dependees off.
-
That was my conclusion as well, however I am at work and it's not appropriate to be reading docker documentation. Thank you for the write up.
-
Komodo is a full management setup, similar to Portainer, Dockge, etc.. It works reasonably well.
Watchtower doesn't require any labeling unless you want to exclude a container.
-
Oh ok, thank you, I already use Portainer for my existing setup so it wouldn't make much sense to fully rework it. I haden't thought of version pinning though so I may implement that instead, it makes sense "breaking changes" wouldn't happen within the same major version.
-
Yes of course. So BSD Truenas is dead? That is a True shame, as BSD is rock steady reliable and runs on truly ancient hardware just fine.
-
on life support thay haven't pulled the plug yet but it is coming. They are not updating anything not urgent and so new hardware support is dead as are jails to do useful things. I'm probably moving to xigmanas in the near future.
-
Yeah pinning is great, you'll still need watchtower for auto updates too
-
Yea for sure, I plan to implement that as well when I have some free time.
-
I switched away from truecharts once scale switched to native docker and my experience has been much smoother since. TC had some kind of breaking change every other month, now I only have to worry about breaking changes when the actual apps have a major update.
The transition was way easier than i expected. First I set up nginx pointing to the TC load balancer for every url, so I could swap apps one at a time. Then I used heavyscript to mount the volumes for an app and rsynced them to a normal dir. With that I could spin up the community apps version or a custom docker config and swap over nginx once I confirmed it was working.
-
Currently I run Talos on a VM on scale. I went with Truecharts. The plan for me is to run it on bare metal at some point.
-
I’m looking at Talos on my Proxmox cluster as VMs. I’m trying to automate it all through ansible and currently stuck trying to bootstrap my secrets manager. Somewhat of an analysis paralysis at the moment. Thinking of using a cloud hosted one with some kind of a local passthrough cache in case the WAN connection gets disrupted.
-
Thst seems like a good option. Ive got some test beds to try it out on
-
I use Debian stable for my main OS for the stability, security and infrequent updates, and run all of my services in Docker containers to keep everything up to date.
-
That's not even to mention declarative, rootless, podman containers via systemd or quadlet!
NixOS Containers can also be a good option if you don't care about rootless.
-
Thanks for a lot of useful replies, everyone. Sorry I ghosted my own post for a couple days.
I’m seeing surprisingly few people who actually use it used TrueNAS, so maybe that’s something to consider moving away from. I’ll have to weigh my options.
