Giuseppe Scrivano

> ``` > > jiazha-mac:~ jiazha$ podman build -t quay.io/olmqe/etcd-index:fips -f catalog.Dockerfile > Error: mkdir /var/tmp/libpod_builder3448793565: no space left on device > ``` the original report was about `rm`, since...

is Ubuntu blocking user namespaces? The same command you've provided, works fine for me on Fedora

the spec behavior is validated by: https://github.com/opencontainers/runtime-tools/blob/master/validation/poststart_fail/poststart_fail.go and that is probably the reason I've implemented it this way for crun. I've no preference on the two behaviors, with the spec...

after this change poststop hooks are now required to be idempotent, even existing ones, as they can be called multiple times. Won't existing hooks fail in most cases when called...

this use case is not supported. fuse-overlayfs will be confused to lookup files on its own mountpoint, as it gets into loops when it uses paths.

@baude, should we store each init container's position in the spec definition and use that to sort the init containers? Otherwise, I don't see any immediate way to do it...

LGTM after the changes suggested above

> It seems set_mempolicy(2) is only effective agains for called threads. I'm not sure how to do it for processes created with exec. Any ideas? the man page says: ```...

without digging further, I'd say it is a kernel issue. a FUSE program should not be able to cause that error, no matter how hard it tries.

> And if there is no existing implementations that are using old/deprecated flags, I'd propose to drop them completely, as it is proven to be impractical over all those years....