Pika

I was curious but good old auto suggest scared me away. It’s concerning when Hestia exploits is one of the suggestions, so I looked into it and saw a few hits. I didn’t investigate them though, I stopped looking then.

Just chiming in, this is not recommended for proxmox

The documentation (FAQ 13) actually directly says that docker should be installed as a QEMU VM on proxmox and that it should not be installed on the Proxmox VE Host

the amount of software I’ve used that lacks this type of system is aggravating. How hard is it to keep an object of property names, and if the name isn’t in it then it errors.

this can be continued into command line as well. if flag -z doesn’t exist, you shouldn’t allow me to run a command with it. It’s clear I am trying to do something (incorrectly) thinking -z is something it isn’t, just error it and tell me that.

Because it’s universal, it works, it’s multi-platform, device agnostic and it’s simple to use user side.

Nothing else available really fits that criteria.

The closest in todays age is probally discord or teams, but neither of which are decentralized. XMPP could work for it, but nobody really uses it anymore and to be honest the standard is ugly as hell to implement.

Browser Notifications are ineffective and have a high probability of failing or not being seen, they are more meant for real-time notices not historical notices not to mention locked to that browser.

App notifications would be amazing for things with apps, but not everyone wants to be forced into using their mobile device for everything, and it would again only be available from said app(unless you do use something like NTFY), which would generally be locked down to a device

Email sucks admin side, but there’s a reason its used.

This is also ignoring the multi-use case that email allows for such as authentication as well, so if its already being stored for accounts, might as well use it for notifications

hard agree, I hate browser notifications with a hard passion, I would never see them if they swapped to that.

my only complaint about it is the lack of clear “hey this is going to be a major update” on the webUI. I did the update command and was met with a different UI. Which wasn’t difficult to figure out, and I have to blame myself for not actually checking the patch notes first, but I wasn’t expecting a major update from the webUI as it only said “new version available run this command to upgrade”

the upgrade as a whole is all and all a great improvement

I’ve recently setup an recipe archival project using tandoor, I’m working on converting all my grandparents fading old as dust cooking recipes from their misc handwritten cursive notecards to digital.

Setup was uneventful but it took a little research to figure out how to use a remote postgres server, turns out the app doesn’t give an error when it can’t connect to the server, it just fails to run

Have to say the actual program itself is absolutely absurd and how they choose their permissions, it breaks all conventional and took quite a bit to get used to.

Yea for sure, I plan to implement that as well when I have some free time.

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.

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/was concidered unhealthy), or having a third party script on the host monitor the dependencies and if one is considered offline, it turns the dependees off.

Looking into it the concern has been approached twice now on the GitHub page, however every time that it’s been brought up it’s been closed for stale because nobody ever replies to the question

I don’t use Watchtower myself for the same reasons described, but I was under the understanding if you had a container as a dependency on another container that if you took the dependency down it also took the container down. Is this not actually true?

I’ve never heard of komodo, I’ve heard a lot about Watchtower but I found it more annoying to set up due to its labeling systems. Is there any added benefit for Komodo over using a standard watch tower setup?

I haven’t set up either of them, but my main concern is having a breaking change be automatically updated

I’ve never used true nass, but I’ve never had any issue with keeping up with releases. I use a proxmox host with Debian containers mostly, and then I use ansible to do any major changes to the hosts such as replacing certificates or upgrading the packages

Being said my backup structure isn’t the most professional, I have a 8 TB external drive that I keep plugged in via USB and I have proxmox backup server on the same host and it creates backups nightly

my router uses openwrt which supports dynamic DNS updating on its own for multiple providers, I currently am through namecheap on it.

I just create the lxc, and if the package requires docker I begrugendly install docker on the lxc, I’ve never had performance issues with Debian lxc, I use it as my base template and it runs flawlessly (outside of ping not working unless sudo)

That being said, I don’t like installing Docker a billion times and I feel like that defeats the purpose of using an lxc in the first place, so for most small Docker containers I just put them on the same lxc since docker is going to handle all the isolation in those anyway

I don’t ZFS though I still use normal EXT4, and I use PBS for backing it up to an external drive, but I’m curious if that may be the root cause of the issues.