Error creating OCI container

N

nullable

New Member
Nov 20, 2025
6
0
1
Hey!

Got this funny response when creating an oci container in Proxmox 9.1.1

"Formatting '/mnt/pve/Store4/images/101/vm-101-disk-0.raw', fmt=raw size=8589934592 preallocation=off
Creating filesystem with 2097152 4k blocks and 524288 inodes
Filesystem UUID: be563e9d-1bfb-49c0-b917-82be562b609a
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632
Detected OCI archive
TASK ERROR: unable to create CT 101 - Error while extracting OCI image: Unknown layer digest sha256:256f393e029fa2063d8c93720da36a74a032bed3355a2bc3e313ad12f8bde9d1 found in rootfs.diff_ids: Unknown layer digest sha256:256f393e029fa2063d8c93720da36a74a032bed3355a2bc3e313ad12f8bde9d1 found in rootfs.diff_ids
"
The image is hosted on docker hub and loads just fine in both docker & podman.
Proxmox downloaded and extracted to a tar file, but I can't start it.

[Update]
FYI: I copied the tar to another box with podman installed, loaded and started the container there without any issues.

Any ideas?
 
Last edited:
that means the OCI image is either invalid or uses some part of the OCI image format spec that we don't support yet, without more details about its contents we probably can't help you..
 
Hi nullable,
you can probably try to copy the image manually with skopeo.
Which should be used under the hood.

Code: 
mkdir ./skop
skopeo copy docker://docker.io/rancher/cowsay:latest dir:./skop

And check if it provides you more verbosity.

BR, Lucas

Edit: It actually does not look like a error during the pull process
 
Last edited:
bl1mp said:
Hi nullable,
you can probably try to copy the image manually with skopeo.
Which should be used under the hood.

Code: 
mkdir ./skop
skopeo copy docker://docker.io/rancher/cowsay:latest dir:./skop

And check if it provides you more verbosity.

BR, Lucas

Edit: It actually does not look like a error during the pull process
Click to expand...
Thanks very much for the suggestion. I ran it successfully, the image was downloaded and extracted with no issues.
Much appreciated, thanks.
 
found the issue, thanks!
 
fabian said:
filed https://bugzilla.proxmox.com/show_bug.cgi?id=7058 for tracking, please subscribe there to follow further developments ;) this would likely need to be fixed in an external dependency of ours..
Click to expand...
Hi Fabian.
I get some of the same error.

I have tried to pull some different images
  • cloudflare/cloudflared:latest
  • netbirdio/netbird:latest
  • linuxserver/grocy:latest
  • koenkk/zigbee2mqtt:latest
I could pull the files to both a NFS share and to a local CT templates directory. Both is converted without any issues. My NFS storage is a Synology NAS.
1) A installation from the local ct directory works fine, and the CT goes online.
2) A installation from the NFS storage is used If I instead tries to create a CT with the file on my NFS share, then I get the error message below.

If I then tries a regular CT with Debian 13 it actually works fine.
I have tried to validate the permissions on Datacenter - Storage. And that is the same.

"TASK ERROR: unable to create CT 100 - Error while parsing OCI image: IO error: Permission denied (os error 13): IO error: Permission denied (os error 13): Permission denied (os error 13)"
 
that's a totally different issue - the container extraction/initialization happens as unprivileged user, and your NFS server doesn't allow unprivileged access.
 
You must log in or register to reply here.
Top Bottom