Closed cgwalters closed 1 month ago
Can someone remind me of the best way to get a debug shell in an osbuild pipeline in bib? cc @mvo5
OK yep there's no /etc/passwd
in osbuild stages, or at least not in the stage running bootc install:
ls: cannot access '/etc/passwd': No such file or directory
https://github.com/containers/bootc/pull/716
Next up is Error: mkdir /etc/containers/networks: read-only file system
as expected
Next up is Error: mkdir /etc/containers/networks: read-only file system as expected :arrow_right: https://github.com/containers/bootc/pull/717
And next up is: Error: initializing source docker://quay.io/fedora/fedora:40: pinging container registry quay.io: Get "https://quay.io/v2/": dial tcp: lookup quay.io on [::1]:53: read udp [::1]:54423->[::1]:53: read: connection refuse
Because it looks like bootc-image-builder is running stages without networking...as expected.
Now, this gets into an important implementation detail. Today bib copies the input container to the osbuild store...I want to avoid that for these bound images as it complicates things and we are not getting value out of the osbuild store today.
IOW I want to just require that bound images live in the container storage used by bib - as that will be maximally erognomic for users.
So to fix this, we'll want to configure the install path invocation to look there as an additional image store or oso.
https://github.com/containers/bootc/pull/719 will get us closer - I didn't yet get it working end-to-end in bib, but it does work with bootc install
in the way I think it should.
Filed https://github.com/osbuild/bootc-image-builder/issues/560 for the bib side discussion
I previously hit https://github.com/containers/podman/issues/22785#issuecomment-2131384748 - this looks like a different one.
Will dig in to see what's going on.