Joseph Marrero Corchado

@cgwalters does this makes sense now in the context of layering?

Cool, I think this will be helpful. I will add it to Jira. CLOSING in favor of: https://github.com/coreos/rpm-ostree/issues/744

No errors with: quay.io/jmarrero_rh/my-custom-fcos:silverblue-2 But: ``` skopeo copy docker://quay.io/jmarrero_rh/my-custom-fcos:silverblue-2 oci:ocidir-good:good-image ``` ``` sha256 tar tvf ff5f4ae9d98fb4869f5bb5ea5e749ccc6f068f7db5b8e7f3505cd0f2262c65ba |grep sysroot drwxr-xr-x 0/0 0 1969-12-31 19:00 sysroot drwxr-xr-x 0/0 0 1969-12-31 19:00 sysroot/ostree...

I think this might be related... Bad image: ``` ./sha256/7cc83e20a3824c08397341669c9ecf07780cc68aaf6352e1692c704d74b5d25d lrwxrwxrwx 0/0 0 1969-12-31 19:00 sysroot/ostree/repo/objects/5d/838fcee94ad472ea96dbc718a965e0674f751b3eb90fb140dd72ad9d0eff06.file -> /usr/share/pki/ca-trust-legacy/ca-bundle.legacy.default.crt hrw-r--r-- 0/0 0 1969-12-31 19:00 usr/share/pki/ca-trust-legacy/ca-bundle.legacy.default.crt link to sysroot/ostree/repo/objects/ea/6b004bc150b3b37d623348c7b77b3486d388f64c3f1138a021b8140d267d0e.file hrw-r--r-- 0/0 0...

Well but in the good build I still have the same behavior: ``` ./sha256/fb6fc1e2e97291ad39dbe53434e19cb244d9eceeedc07a0c0b094cf0cc7aefc0 hrw-r--r-- 0/0 0 1969-12-31 19:00 sysroot/ostree/repo/objects/ea/6b004bc150b3b37d623348c7b77b3486d388f64c3f1138a021b8140d267d0e.file-xattrs-link link to sysroot/ostree/repo/objects/98/223daccac009b54901f56d64902ae3c54f248baea8bf9da4d35a4a69006e3a.file-xattrs -rw-r--r-- 0/0 0 1969-12-31 19:00 sysroot/ostree/repo/objects/ea/6b004bc150b3b37d623348c7b77b3486d388f64c3f1138a021b8140d267d0e.file hrw-r--r--...

@cgwalters We are looking at https://github.com/coreos/rpm-ostree/pull/4099 as a template to implement this. As a first pass concentrating on the daemon side, maybe a second PR is dealing with the container...

https://github.com/coreos/rpm-ostree/releases/tag/v2022.16 includes the fix and I verified it works now with my silverblue setup as well. Thank you Colin!

Well, I should have checked better. Today I noticed I was still pulling from the image built with docker and not the podman one and noticed this: ``` ~ rpm-ostree...

Ignore my last comment, I am guessing I had some weird combination of packages between the images. I reset my install and rebased on the supposedly bad image. And it...

Makes sense, if I see it again I will create a new bug.