install: Optionally use host mounted /var/lib/containers
#286
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I just keep hitting the host skopeo requirement in corner cases; it's annoying because otherwise the container is self-sufficient. Change our installation instructions to add a
/var/lib/containers
bind mount.For the time being of course we continue to support forking off
skopeo
on the host.One thing I still want to investigate is dropping some requirements here and switch to dynamically setting up the mount points inside the container as is mentioned in https://brauner.io/2023/02/28/mounting-into-mount-namespaces.html but this currently requires relatively new host kernels.
As far as test coverage, this changes the Github Action that uses ubuntu and needed to build a newer skopeo to stop doing that, and in fact we explicitly remove skopeo to verify it's not being used in the install process.
I didn't change the other install tests to verify they keep working.
Closes: #81