To manage your own registry using the OCI APIs, there's a variety of client tooling.
- I'm the author of #regclient (the regsync command is very useful for mirrors): https://regclient.org
- #Crane is available from Google: https://github.com/google/go-containerregistry/tree/main/cmd/crane
- #Oras was started by Microsoft: https://oras.land/
- #Skopeo is available from RedHat: https://github.com/containers/skopeo/
@alxlg your most welcome!
I by no means only use #docker. Far from it. 
But it does have a lot of capabilities now. Very much thanks to the outstanding work done on #podman and #buildah.
Heck, yesterday a colleague found out "they" copied #skopeo for image mirroring with "imagetools". The cli design is really noisy, but it does work. 
https://docs.docker.com/reference/cli/docker/buildx/imagetools/create/
Skopeo can also inspect the configuration of a container, not just what's in the OCI manifest. It's great to get a handle on the default environment variables, working directory, and other defaults. Use the --config flag to get the configuration of an image as a big JSON file.
skopeo inspect --config --override-os="linux" --override-arch="amd64" docker://python:3.12
I also needed to specify the OS and CPU architecture I wanted to inspect. Skopeo defaults to what's detected on the host and I'm on an ARM-based Mac. This returns something that's easy to pipe through JQ for just what I need - in this case, the default environment variables of the Python:3.12 image for Intel-based Linux systems.
ᐅ skopeo inspect --config --override-os="linux" --override-arch="amd64" docker://python:3.12 | jq '.config.Env'
[
"PATH=/usr/local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin",
"LANG=C.UTF-8",
"GPG_KEY=7169605F62C751356D054A26A821E680E5FA6305",
"PYTHON_VERSION=3.12.7",
"PYTHON_SHA256=24887b92e2afd4a2ac602419ad4b596372f67ac9b077190f459aba390faf5550"
]
Red Hat to Contribute Comprehensive Container Tools Collection to Cloud Native Computing Foundation https://www.redhat.com/en/blog/red-hat-contribute-comprehensive-container-tools-collection-cloud-native-computing-foundation #RedHat #CNCF #podman #bootc #skopeo #buildah #OpenSource #Linux
Today at #KubeCon, Red Hat announced their intent to contribute their container tools such as #Podman, #PodmanDesktop, #Skopeo, #Buildah to the Cloud Native Computing Foundation! Super exciting news & proof of the commitment Red Hat has to the Open Source community.
Will I be glad that I found #skopeo? Perhaps this next week will demonstrate.
Looks like it is finally time for my 6-year old to join the IT department. 
#buildah #cri_o #openshift #podman #skopeo #coloring_book
https://docs.fedoraproject.org/en-US/fedora-sericea/_attachments/container-commandos.pdf
Next up, making multi-arch container images with #buildroot and #skopeo … #OpenSource
Want to know how big an image is going to be *before* you download it? You can do this with #skopeo and a bit of #bash.
skopeo inspect docker://alpine/openssl:latest | jq '.LayersData[].Size' | paste -s -d+ - | bc | numfmt --to=iec-i --suffix=B
3.6MiB
skopeo inspect docker://ucsb/pstat-134-234:v20231107 | jq '.LayersData[].Size' | paste -s -d+ - | bc | numfmt --to=iec-i --suffix=B
7.6GiB
Most probably, if you are working with containers, you use some client-side tooling to work with remote container registries. At that point, there are some helper tools that come in handy like #skopeo, #crane, and #regctl 
A great blog by @d2iq_eng
https://eng.d2iq.com/blog/a-tale-of-two-container-image-tools-skopeo-and-crane/
I've just started using #crane instead of #skopeo (both great tools!) in #mindthegap so wrote up a quick blog post showcasing both tools and a few of their differences
https://eng.d2iq.com/blog/a-tale-of-two-container-image-tools-skopeo-and-crane/
I love how much of my job is automated via #Ansible #AWX and #Jenkins. I love how amazing the #RedHat #container tools are for supporting it all - #podman, #skopeo, #toolbx, etc. It's all running on a highly versatile and fully #opensource stack.
quicktip #19: inspecting remote Windows container images without downloading them using Skopeo.
(to not having to run run a Linux container for Skopeo, we'll build skopeo.exe for Windows).
