I played with this a bit today. Only downside is, no easy way to update containers yet. But on the other hand, no more dealing with macvlan or custom docker networks.
dijit•59m ago
“update”, I assume you mean “recreate with new image”?
I think docker itself doesn’t support that.
doubled112•52m ago
I use Docker compose to recreate containers with a new image regularly.
I'm sure you could be creative with volumes in Proxmox and build a new LXC container from a new OCI image with the old volumes attached.
dijit•51m ago
> I use Docker compose to recreate containers with a new image regularly.
try doing so without the compose file though.
doubled112•48m ago
That's true, isn't it? It was one of those features you'd think they would have had figured out, but no.
prmoustache•27m ago
Isn't the ability to do blue/green deployments, canary releases and easy rollbacks huge incentives to use containers?
I think virtually nobody cares about being able to change the image of a container when you can so easily start a new one.
danudey•3m ago
The idea is that your container image is the thing you want, and is (relatively) immutable, so you delete and create containers when you want things to change. If you need state you can do that with volume mounts, but the idea is that you don't need to 'update' a container, you just replace it with a new one.
That's also what docker compose does, under the hood. It doesn't 'update' a container, it just deletes it and recreates it with the new image and the same settings/name/ports/volumes/etc.
k__•57m ago
Is this similar to what FlyIO is doing? Running containers as microVMs?
indigodaddy•24m ago
Perhaps in spirit? But I don't think you can term LXC a microVM, and I doubt they start close to as fast as Firecracker or smolbsd, and similar ilk. EDIT - appears I am probably wrong about firecracker being faster than LXC as LXC is kernel based virtualization and likely has faster startup than microVMs?
_ache_•26m ago
I have an "error" "I am not a teapot"
719 - I am not a teapot
Espresso Web (Red Hat Enterprise Linux) at raymii.org
Looks suspicious, ... not 418, 719.
radiator•9m ago
I think 418 is 'I am a teapot' so it would not be correct to use it in your case. 719 must be a typo though, perhaps it should be 419.
dizhn•9m ago
They are converted to LXC images then run. No compose file either. Still pretty neat.
nirav72•1h ago
dijit•59m ago
I think docker itself doesn’t support that.
doubled112•52m ago
I'm sure you could be creative with volumes in Proxmox and build a new LXC container from a new OCI image with the old volumes attached.
dijit•51m ago
try doing so without the compose file though.
doubled112•48m ago
prmoustache•27m ago
I think virtually nobody cares about being able to change the image of a container when you can so easily start a new one.
danudey•3m ago
That's also what docker compose does, under the hood. It doesn't 'update' a container, it just deletes it and recreates it with the new image and the same settings/name/ports/volumes/etc.