nostr:npub1l3gpk6vrudg8r67swqlex5alv9ch59s4lw46kk6hekuxe2n3aczsyqvu48
> They talk about it like it's just another installation avenue like flatpak
That's actually a very good comparison. Docker is kind of like FlatPak for servers. Although maybe more like AppImage.
As long as you have the latest image, you have the latest version of everything packaged inside it. Like any package manager, this can be automated. Everything else is handled by the OS, not Docker or the Container. That's my understanding, having only tinkered with Docker a little.
nostr:npub17j5xgxhtskpcp0kjd9ldjhm3w6ggns7kkvfp44lk4qsrdwawmjeqvd0ny5
nostr:npub1trdnqrfstufc45awha43p6xy2n0v6czuhapzh4r09hap08dg0c6s9gussx nostr:npub17j5xgxhtskpcp0kjd9ldjhm3w6ggns7kkvfp44lk4qsrdwawmjeqvd0ny5
The difference being that flatpak is pretty committed to keeping everything quite up-to-date.
With containers, YMMV.
I'm not intending to dog on containers, but I'm just surprised that I don't hear *anyone* talking about the potential risks.
Zero risk isn't possible, but it's good to be aware of them and plan/decide accordingly.
No replies yet.
