Ancestors

Written by foremanguy on 2024-12-12 at 18:46

My thoughts on docker

https://lemmy.ml/post/23510440

=> More informations about this toot | More toots from foremanguy92_@lemmy.ml

Written by PerogiBoi@lemmy.ca on 2024-12-12 at 19:39

I don’t like docker. It’s hard to update containers, hard to modify specific settings, hard to configure network settings, just overall for me I’ve had a bad experience. It’s fantastic for quickly spinning things up but for long term usecase and customizing it to work well with all my services, I find it lacking.

I just create Debian containers or VMs for my different services using Proxmox. I have full control over all settings that I didn’t have in docker.

=> More informations about this toot | More toots from PerogiBoi@lemmy.ca

Written by beerclue@lemmy.world on 2024-12-12 at 20:17

What do you mean it’s hard to update containers?

=> More informations about this toot | More toots from beerclue@lemmy.world

Written by MaggiWuerze on 2024-12-12 at 23:44

For real. Map persistent data out and then just docker compose pull && up. Theres nothing to it. Regular backups make reverting to previous container versions a breeze

=> More informations about this toot | More toots from MaggiWuerze@feddit.org

Toot

Written by non_burglar@lemmy.world on 2024-12-14 at 13:06

For one, if the compose file syntax or structure and options changes (like it did recently for immich), you have to dig through github issues to find that out and re-create the compose with little guidance.

Not docker’s fault specifically, but it’s becoming an issue with more and more software issued as a docker image. Docker democratizes software, but we pay the price in losing perspective on what is good dev practice.

=> More informations about this toot | More toots from non_burglar@lemmy.world

Descendants

Written by MaggiWuerze on 2024-12-14 at 14:30

Since when is checking for breaking changes a problem? You should do that every time you want to update. The Immich devs make a real good informing bout those and Immich in general is a bad example since it is still in so early and active development

=> More informations about this toot | More toots from MaggiWuerze@feddit.org

Written by non_burglar@lemmy.world on 2024-12-14 at 17:03

I’m trying to indicate that docker has its own kinds of problems that don’t really occur for software that isn’t containerized.

I used the immich issue because it was actually NOT indicated as a breaking change by the devs, and the few of us who had migrated the same compose yml from older veraions and had a problem were met with “oh, that is a very old config, you should be using the modern one”.

Docker is great, but it comes with some specific understanding that isn’t necessarily obvious.

=> More informations about this toot | More toots from non_burglar@lemmy.world