▲ | modeless 4 days ago | ||||||||||||||||||||||||||||||||||
It's very silly that Docker didn't work this way to start with. Thank you, it looks cool! | |||||||||||||||||||||||||||||||||||
▲ | TheRoque 4 days ago | parent [-] | ||||||||||||||||||||||||||||||||||
You can already achieve the same thing by making your image into an archive, pushing it to your server, and then running it from the archive on your server. Saving as archive looks like this: `docker save -o may-app.tar my-app:latest` And loading it looks like this: `docker load -i /path/to/my-app.tar` Using a tool like ansible, you can achieve easily what "Unregistry" is doing automatically. According to the github repo, save/load has the drawback of tranfering the whole image over the network, which could be an issue that's true. And managing the images instead of archive files seems more convenient. | |||||||||||||||||||||||||||||||||||
|