Reid Priedhorsky

The system call that fails is this: ``` setxattr("/proc/self/fd/4", "system.posix_acl_access", "\2\0\0\0\1\0\7\0\377\377\377\377\4\0\5\0\377\377\377\377\10\0\5\0\4\0\0\0\20\0\5", 44, 0) = -1 EINVAL (Invalid argument) ``` I believe the problem is that `system` attributes (or possibly a...

I can’t reproduce and `--xattrs` is no longer the default, so demoting. ``` $ export CH_IMAGE_STORAGE=$NFS/storage $ printf 'FROM redhat/ubi8:latest\nRUN true\n' | ch-image build --xattrs -t foo - 1. FROM...

Does this really mean OCI images, with a tarball per layer?

I can't reproduce (master branch): ``` $ ch-image build -t leap -f - /tmp

On point 3 at least, `/var/tmp` is very standard so should almost always be available.

I can reproduce it: ``` $ ch-image pull docker.io/boutproject/release:4.2 pulling image: docker.io/boutproject/release:4.2 requesting arch: amd64 error: not in registry: docker.io:443/boutproject/release:4.2 ``` Adding `-vvv` reveals that the URL it tries for...

This still happens, though the error is different: ``` $ ch-image pull boutproject/release:4.2 [...] done $ ch-image pull docker.io/boutproject/release:4.2 pulling image: docker.io/boutproject/release:4.2 requesting arch: amd64 error: GET failed; expected status...

See also #846.

See also #1068.

@j-ogas I agree. Can you make a new issue for that?