11–20 of 178 posts
Earlier quoted context omitted.
Thank you! Can you please clarify what kind of support you mean for docker compose?
I assume that he means "rather than pushing up each individual container for a project, it could take something like a compose file over a list of underlying containers, and push them all up to the endpoint."
What’s the difference between this and skopeo? Is it the ssh support ? I’m not super familiar with skopeo forgive my ignorance https://github.com/containers/skopeo
How about using docker context. I use that a lot and works nicely.
FWIW I've been saving then using mscp to transfer the file. It basically does multiple scp connections to speed it up and it works great.
What’s the difference between this and skopeo? Is it the ssh support ? I’m not super familiar with skopeo forgive my ignorance https://github.com/containers/skopeo
"skopeo" seems to related to managing registeries, very different from this.
Ooh this made me discover uncloud. Sounds like exactly what I was looking for. I wanted something like dokku but beefier for a sideproject server setup.
A quick and dirty version: docker -H host1 image save IMAGE | docker -H host2 image load note: this isn't efficient at all (no compression or layer caching)!
docker save $image | bzip2 | ssh "$host" 'bunzip2 | docker load'