I wish containers hadn't created the abstractions of a registry and an image instead of exposing it all as tar files (which is what it kind of is under the covers) served over a glorified file server. This leads to people assuming there's some kind of magic happening and that the entire process is very arcane, when in reality it's just unpacking tar files.<p>If you want to DIY a container with unix tools, this should help: <a href="https://containers.gitbook.io/build-containers-the-hard-way/" rel="nofollow">https://containers.gitbook.io/build-containers-the-hard-way/</a>
It's interesting skopeo [1] hasn't popped up in this discussion, partially because it is part of redhat's container tools along with podman, and partially because although it started out as a tool to examine remote containers it too supports container migration, but not just between registries.<p>From the linked website "Skopeo is a tool for moving container images between different types of container storages. It allows you to copy container images between container registries like docker.io, quay.io, and your internal container registry or different types of storage on your local system". Perhaps redhat plan to roll up skopeo functionality into Podman at some point?<p><a href="https://www.redhat.com/en/blog/skopeo-10-released#:~:text=Skopeo%20is%20a%20tool%20for,storage%20on%20your%20local%20system" rel="nofollow">https://www.redhat.com/en/blog/skopeo-10-released#:~:text=Sk...</a>.
Containerd and nerdctl have the neat trick of (experimental) support for distributing images over IPFS: <a href="https://github.com/containerd/nerdctl/blob/master/docs/ipfs.md" rel="nofollow">https://github.com/containerd/nerdctl/blob/master/docs/ipfs....</a>
It's unclear if this will be faster if the image already exists (layers exist).<p>a docker push/docker pull can skip layers that already exist.
Anybody know of some simple/lighweight registry for local usage? Quay boasts itself as a super duper enterprisey all solution. I'm looking for something more of a 'simple http server with basic acl' solution.
I use this trick to push to servers in an unnecessarily tight network I have to deploy to sometimes that can't see my source control / container registry.<p>But I do it for Docker. I have overall the sense that Podman is trying to accomplish feature parity with Docker but isn't there yet. Feedback on this formulation?