Ancestors

Written by machinin@lemmy.world on 2024-12-22 at 10:21

Docker on VM vs bare install on VM

https://lemmy.world/post/23413638

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

Written by Scott on 2024-12-22 at 10:30

Containers are just processes with flags. Those flags isolate the process’s filesystem, memory, etc.

The advantages of containers is that the software dependencies can be unique per container and not conflict with others. There are no significant disadvantages.

Without containers, if software A has the same dependency as software B but need different versions of that dependency, you’ll have issues.

=> More informations about this toot | More toots from scott@lem.free.as

Written by machinin@lemmy.world on 2024-12-22 at 11:47

Thanks for this - the one advantage I’m noticing is that too update the services I’m running, I have to rebuild the container. I can’t really just update from the UI if an update is available. I can do it, it is just somewhat of a nuisance.

How often are there issues with dependencies? Is that a problem with a lot of software these days?

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

Written by Passerby6497@lemmy.world on 2024-12-22 at 15:39

But rebuilding your container is pretty trivial from the command line all said and done. I have something like this alias’d in my .bashrc to smooth it along:

Docker compose pull; docker compose down; docker compose up -d

I regularly check on my systems and go through my docker dirs and run my alias to update everything fairly simply. Add in periodic schedule image cleanups and it has been humming along for a couple years for the most part (aside from one odd software issues and hardware failures).

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

Written by tofubl@discuss.tchncs.de on 2024-12-22 at 20:54

Is there a specific reason you’re taking the services down before bringing them back up? Just docker compose up -d recreates all services that had a new image pulled, but leaves the others running.

=> More informations about this toot | More toots from tofubl@discuss.tchncs.de

Toot

Written by Passerby6497@lemmy.world on 2024-12-22 at 21:09

Probably just a hold over from when I was first learning. Had issues with a couple services not actually updating without it, so I just do it to be absolutely sure. Also, I only ever run one app per compose, so that forces a “reboot” of the whole stack when I update.

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

Descendants