Felix Obenhuber

Puh. This requires very detailed knowledge in order to get setup. My feeling for the future is more to get rid of formats and focus on the formats used by...

Closing this. The compatibility check is flaky anyways.

Check the top-level error printing in the example main. Maybe debug printing the error instead of using `Display` helps here. This issues relates to #340 which should check exactly those...

Runtime checks configured directories with permissions etc. Everything else is a runtime error.

Note: If a container is started with it's own namespace (the namespace is created by the runtime) it's possible to listen on a socket in there instead of passing a...

Postponed until `tokio::task::Builder` is stabablized: https://github.com/tokio-rs/tokio/issues/4114

It's not possible to install a container with the same identification twice in two repositories. The only way to get into the error situation that there are two identical entities...

Two identical container (name and version) are not possible. The runtime refuses to start (fails on repository initialisation).

Today we have strace that can be opt in for a container launch. The example main provides a flag to disable the mount namespace for rootfs inspection. Checkin the rootfs...

Closing this because `strace` is considered the the most useful thing in place along with logs.