If you are really trying to do things inside your container after it's deployed, you're probably misusing microservice containers, and/or you haven't deployed sufficient MELT to know what your containerized applications are doing.
If you're using Docker just to run a VM, there are better options out there.
JustSomeDevGuy
Are you kubernetesing it? What about ye ole Helm charts?
FRIENDisCHUMisBAIT
And he passed away thirteen years ago. RIP
vurcease
Well then Apple has just the announcement for you, then! https://github.com/apple/container
GeorgeCostabaplaps
Just pull a new image
Shaows
The shoes or the program?
RedTailedHawk
Or the pants?
WhatSayYouCitizen
... for building or deploying?
MHammett
Between the two, I would say deployment, but the deployment is the easy part. Using it afterwards, not so much.
WhatSayYouCitizen
If you are really trying to do things inside your container after it's deployed, you're probably misusing microservice containers, and/or you haven't deployed sufficient MELT to know what your containerized applications are doing.
If you're using Docker just to run a VM, there are better options out there.
LeekofLegend
Neither, his boyfriend's nickname is the docker
WhatSayYouCitizen
mypylon
then find another container solution
MHammett
I much prefer LXC in Proxmox, but I often have to work with things that others have created.
mypylon
Yes, I know 'bow to the absurd' very well.