Currently, when trying to run OCI bundles with a too new version UXC errors out with the following:
Sun May 3 12:37:40 2026 user.err : jail: unsupported ociVersion 1.2.1
Sun May 3 12:37:40 2026 user.err : jail: parsing of OCI JSON spec has failed: Not supported (95)
This occurs here.
Note that version 1.2.1 is the version current Podman (5.8.2) generates with 1.3 being in the current main branch.
UXC claims to be a drop in replacement for runc and crun, however this behaviour is not consistent with them. See this issue and this commit which happened over two years ago.
UXC should not throw an error but a warning only if the OCI version is to high. Or at least, this should be configurable. Since this way UXC isn't useful for its purpose to be used as a crun/runc replacement in OpenWRT when current container managers generate OOR spec bundles.
Edit: After patching podman to force it to generate OCI v1.0.3 bundles (1.0.2 but podman uses 1.0.3 internally) I now get user.err : jail: parsing of OCI JSON spec has failed: Operation not permitted (1) which confuses me even more since I've looked through the code and didn't find any way for it to generate EPERM errors
Currently, when trying to run OCI bundles with a too new version UXC errors out with the following:
This occurs here.
Note that version 1.2.1 is the version current Podman (5.8.2) generates with 1.3 being in the current main branch.
UXC claims to be a drop in replacement for runc and crun, however this behaviour is not consistent with them. See this issue and this commit which happened over two years ago.
UXC should not throw an error but a warning only if the OCI version is to high. Or at least, this should be configurable. Since this way UXC isn't useful for its purpose to be used as a crun/runc replacement in OpenWRT when current container managers generate OOR spec bundles.
Edit: After patching podman to force it to generate OCI v1.0.3 bundles (1.0.2 but podman uses 1.0.3 internally) I now get
user.err : jail: parsing of OCI JSON spec has failed: Operation not permitted (1)which confuses me even more since I've looked through the code and didn't find any way for it to generate EPERM errors