Failure in install to-filesystem: Testing install_t: No such file or directory

[cgwalters]

(Copy-pasting a question asked in private chat)

The command 'bootc install to-filesystem --stateroot=default --source-imgref=containers-storage:quay.io/centos-bootc/centos-bootc:stream9 --target-imgref=containers-storage:quay.io/centos-bootc/centos-bootc:stream9 default' exited with the code 1:
ERROR Installing to filesystem: Ensuring selinux install_t type: Ensuring selinux install_t type: Testing install_t: No such file or directory (os error 2)

So first thing here is we search for the error message.

It looks to me like we may somehow be missing chcon from this environment?

[cgwalters]

It'd be helpful to know more about the outer environment here. I think this may be part of rhinstaller/anaconda#5197 ?

And in this environment, we're invoking bootc install outside of the target container image, right? So it may be that we're missing that runtime dependency.

I think we should probably change the code to not invoke chcon actually.

[jkonecny12]

Hi, this is interesting. I wonder if we don't need to just add the missing dependency to bootc?

[cgwalters]

➡️ #1391

[elkoniu]

Yes, that is correct - it is a part of bootc install being supported by anaconda :)

[elkoniu]

Interesting thing I found during testing. In #1391 chcon has been added to bootc.spec file. I am afraid it may be removed anyway by lorax following the cleanup template https://github.com/weldr/lorax/blob/master/share/templates.d/99-generic/runtime-cleanup.tmpl#L118 I guess this means separated PR updating lorax template is needed to be sure chcon will stay.

[elkoniu]

Lorax PR fixing this: weldr/lorax#1477

[elkoniu]

One steep closer, this time bootc complains about missing /etc/ostree/prepare-root.conf file:

ERROR Installing to filesystem: Failed to find ostree/prepare-root.conf in /usr/lib or /etc

I have created fake one with the content:

[composefs]
enabled = yes

If again some dependency package may be missing when bootc is being called not from the container context?