[pve-devel] [PATCH container/proxmox{, -perl-rs}/storage 0/9] support OCI images as container templates

[Filip Schauer]

On 02/06/2025 18:26, Michael Köppl wrote:
> Thanks for tackling this! I tested setting up containers based on
> various OCI images. Apart from the UI not allowing upload of .tar files
> (see my comment on the pve-storage patch), the uploading worked as
> expected. I encountered some problems with various images during my
> testing. I used docker save to get the .tar files (as per your example).
> Tested the following with that setup:
>
> - httpd image (as per your example): worked as expected, was able to
> reach the httpd "It works!" page
> - redis:latest: connection reset by peer on start, fails to start
> - debian:bookworm: `sync_wait: 34 An error occurred in another process
> (expected sequence number 7)` on start
> - alpine:latest: worked as expected, landed in shell
> - fedora:latest: unable to open file
> '/etc/systemd/system-preset/00-pve.preset.tmp.85271' - No such file or
> directory on create, cannot create container
> - ubuntu:latest: `unable to open file
> '/etc/systemd/network/eth0.network.tmp.89496' - No such file or directory`
> - Supplying an SSH key does not seem to work (tested with alpine OCI image)

Thanks for testing! These errors should be fixed with v2.

> - Images with a CMD in their Dockerfile that does not call a shell (i.e.
> last line is not CMD ["/bin/bash"]) will not display anything in the
> console view. This is not unexpected, but UX-wise it might make sense to
> inform users about this in some way (maybe by disabling the console view
> and displaying an informational message)

This sounds like it was caused by the fact that I dropped the CMD
parameter by mistake. Should be fixed with v2.