skopeo

I think the most common tools for similar workflows is Google's crane[0] and Red Hat's Skopeo[1]. It might be slightly more low-level than most developers want, though. [0]: https://github.com/google/go-containerregistry/blob/v0.20.7/... [1]: https://github.com/containers/skopeo

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

You can rip a rootfs from a docker image using skopeo[1] and undocker[2] then you can puppeteer it with bwrap[3]. This works for most linux distributions (they behave well as fakeroot puppets). Package managers from Debian-based distros tend to misbehave in bwrap in my experience. I use this method to obtain software from various distro repositories or when RPM packages are distributed by vendors. [1] <https://github.com/containers/skopeo> [2] <https://git.jakstys.lt/motiejus/undocker> [3] <https://github.com/containers/bubblewrap>

I believe skopeo should allow you to: https://github.com/containers/skopeo

Self hoisting here, I put this together to make it easier to generate single (extra) layer docker images without needing a docker daemon, capabilities, chroot, etc: https://github.com/andrewbaxter/dinker Caveat: it doesn't work on Fly.io. They seem to be having some issue with OCI manifests: https://github.com/containers/skopeo/issues/1881 . They're also having issues with new docker versions pushing from CI: https://community.fly.io/t/deploying-to-fly-via-github-actio... ... the timing of this post seems weird. FWIW the article says > create a Docker image, also known as an OCI image I don't think this is quite right. From my investigation, Docker and OCI images are basically content addressed trees, starting with a root manifest that points to other files and their hashes (root -> images -> layers -> layer configs + files). The OCI m

You can use Skopeo[1] to easily migrate your images from one registry to another. Here it is from Package Registry to Container Registry. A personal access token with `write:packages` and `read:packages` scopes is enough. skopeo copy \ --src-creds <USER>:<ACCESS_TOKEN> \ --dest-creds <USER>:<ACCESS_TOKEN> \ docker://docker.pkg.github.com/<USER>/<REPO>/<IMG>:<VER> \ docker://ghcr.io/<USER>/<IMG>:<VER> [1] https://github.com/containers/skopeo

Yeah, it is cool, but it feels more like a demo for nix. If you want to create docker image of your own app, you probably would use: https://nixos.org/nixpkgs/manual/#sec-pkgs-dockerTools This will produce an exported docker image as tar file, which then you can import it using either docker, or tool like skopeo[1] (which is also included in nixpkgs). The nix-shell functionality is also quite nice, because it allows you to create common development environment, with all tooling available that one might need to work. [1] https://github.com/containers/skopeo