Otherwise it just does skopeo copy docker://$reference oci-archive:$path/$filename.tar.
With$reference=registry.example.org/name, $path=PVE::Storage::get_vztmpl_dir($cfg, $storage) (/var/lib/vz/template/cache in my case), $filename = PVE::Storage::normalize_content_filename($reference).
We then would have for hello-world image: skopeo copy docker://docker.io/hello-world:latest oci-archive:/var/lib/vz/template/cache/hello-world_latest.tar
Otherwise it just does skopeo copy docker://$reference oci-archive:$path/$filename.tar.
With$reference=registry.example.org/name, $path=PVE::Storage::get_vztmpl_dir($cfg, $storage) (/var/lib/vz/template/cache in my case), $filename = PVE::Storage::normalize_content_filename($reference).
We then would have for hello-world image: skopeo copy docker://docker.io/hello-world:latest oci-archive:/var/lib/vz/template/cache/hello-world_latest.tar
Ok cool, will wait patiently for the next release.
Thanks, didn’t know about skopeo. But since my last reply I’m using the API already in combination with Ansible. Works excellent in quickly spin up OCI LXC’s
Next project for me will be using an entire docker compose file/paste to create OCI LXC’s automatically, including adding the given env vars to the LXC. I’m a bit confused on how to put multiple in one LXC, honestly, I don’t think this is possible. I want to find a way to reduce the manual steps even further and I’m having fun learning this way.