setup.ValidateHasContainerTags: support use in rootless containers#447
Merged
achilleas-k merged 1 commit intomainfrom Feb 12, 2026
Merged
setup.ValidateHasContainerTags: support use in rootless containers#447achilleas-k merged 1 commit intomainfrom
achilleas-k merged 1 commit intomainfrom
Conversation
d829632 to
6d8d28f
Compare
alexlarsson
added a commit
to osbuild/images
that referenced
this pull request
Feb 2, 2026
When running in a rootless container (made possible via osbuild/bootc-image-builder#1189) then generally the per-user container store is passed to bc-i-b, both because that makes sense, but also because the container doesn't have permissions to read the host store. This is typically done by passing `-v ~/.local/share/containers/storage:/var/lib/containers/storage` when running bc-i-b in podman. Unfortunately when this happens, podman complains that the store is in the wrong place: ``` Error: database static dir "/home/alex/.local/share/containers/storage/libpod" does not match our static dir "/var/lib/containers/storage/libpod": database configuration mismatch ``` To fix this, we pass in podman arguments `--root` and `--imagestore` to set up an environment where the graphroot is some empty directory that has the "correct" location and we only load the image layers from /var/lib/containers. To ensure this doesn't weirdly affect the regular case, this is all protected by podmanutil.IsRootless(). Note: This is similar to what is done in osbuild/image-builder-cli#447 and it has a local copy of podmanutil.IsRootless() from image-builder-cli.
This was referenced Feb 2, 2026
lzap
reviewed
Feb 6, 2026
Contributor
lzap
left a comment
There was a problem hiding this comment.
Can you show how the problem manifests? I haven't tried rootless bootc yet myself but now is the time I guess.
Contributor
Author
I'm not sure what more description you want? The description has the exact error message you will get. |
6d8d28f to
58bb48d
Compare
When running in a rootless container (made possible via osbuild/bootc-image-builder#1189) then generally the per-user container store is passed to bc-i-b, both because that makes sense, but also because the container doesn't have permissions to read the host store. This is typically done by passing `-v ~/.local/share/containers/storage:/var/lib/containers/storage` when running bc-i-b in podman. Unfortunately when this happens, podman complains that the store is in the wrong place: ``` Error: database static dir "/home/alex/.local/share/containers/storage/libpod" does not match our static dir "/var/lib/containers/storage/libpod": database configuration mismatch ``` To fix this, we pass in podman arguments `--root` and `--imagestore` to set up an environment where the graphroot is some empty directory that has the "correct" location and we only load the image layers from /var/lib/containers. To ensure this doesn't weirdly affect the regular case, this is all protected by podmanutil.IsRootless().
58bb48d to
73f6c53
Compare
Contributor
|
Do we have any tests that cover this? |
Contributor
Author
|
@bcl Its not so easy to test this particular change, but once we have all the required changes landed we will want to have a test of the entire thing (i.e. a rootless bootc-image-builder run). |
achilleas-k
approved these changes
Feb 12, 2026
github-merge-queue bot
pushed a commit
to osbuild/images
that referenced
this pull request
Feb 12, 2026
When running in a rootless container (made possible via osbuild/bootc-image-builder#1189) then generally the per-user container store is passed to bc-i-b, both because that makes sense, but also because the container doesn't have permissions to read the host store. This is typically done by passing `-v ~/.local/share/containers/storage:/var/lib/containers/storage` when running bc-i-b in podman. Unfortunately when this happens, podman complains that the store is in the wrong place: ``` Error: database static dir "/home/alex/.local/share/containers/storage/libpod" does not match our static dir "/var/lib/containers/storage/libpod": database configuration mismatch ``` To fix this, we pass in podman arguments `--root` and `--imagestore` to set up an environment where the graphroot is some empty directory that has the "correct" location and we only load the image layers from /var/lib/containers. To ensure this doesn't weirdly affect the regular case, this is all protected by podmanutil.IsRootless(). Note: This is similar to what is done in osbuild/image-builder-cli#447 and it has a local copy of podmanutil.IsRootless() from image-builder-cli.
alexlarsson
added a commit
to osbuild/bootc-image-builder
that referenced
this pull request
Feb 12, 2026
This adds the commits from: * osbuild/image-builder-cli#447 * osbuild/images#2167 And with this, we can run a rootless bc-i-b run without any workarounds related to the container store: ``` $ podman run --rm --security-opt label=type:unconfined_t -ti --privileged \ --network=none -v $PWD/output:/output \ -v ~/.local/share/containers/storage:/var/lib/containers/storage \ localhost/bootc-image-builder --in-vm \ --rootfs ext4 --type raw \ quay.io/fedora/fedora-bootc:43 ``` Note: For the above to work, localhost/bootc-image-builder needs to be in the user container store.
alexlarsson
added a commit
to osbuild/bootc-image-builder
that referenced
this pull request
Feb 12, 2026
…work This adds the commits from: * osbuild/image-builder-cli#447 * osbuild/images#2167 And with this, we can run a rootless bc-i-b run without any workarounds related to the container store: ``` $ podman run --rm --security-opt label=type:unconfined_t -ti --privileged \ --network=none -v $PWD/output:/output \ -v ~/.local/share/containers/storage:/var/lib/containers/storage \ localhost/bootc-image-builder --in-vm \ --rootfs ext4 --type raw \ quay.io/fedora/fedora-bootc:43 ``` Note: For the above to work, localhost/bootc-image-builder needs to be in the user container store.
alexlarsson
added a commit
to alexlarsson/bootc-image-builder
that referenced
this pull request
Feb 12, 2026
…work The new versions are images 0.240.0 and ib-cli v49. This adds the commits from: * osbuild/image-builder-cli#447 * osbuild/images#2167 And with this, we can run a rootless bc-i-b run without any workarounds related to the container store: ``` $ podman run --rm --security-opt label=type:unconfined_t -ti --privileged \ --network=none -v $PWD/output:/output \ -v ~/.local/share/containers/storage:/var/lib/containers/storage \ localhost/bootc-image-builder --in-vm \ --rootfs ext4 --type raw \ quay.io/fedora/fedora-bootc:43 ``` Note: For the above to work, localhost/bootc-image-builder needs to be in the user container store.
github-merge-queue bot
pushed a commit
to osbuild/bootc-image-builder
that referenced
this pull request
Feb 12, 2026
…work This adds the commits from: * osbuild/image-builder-cli#447 * osbuild/images#2167 And with this, we can run a rootless bc-i-b run without any workarounds related to the container store: ``` $ podman run --rm --security-opt label=type:unconfined_t -ti --privileged \ --network=none -v $PWD/output:/output \ -v ~/.local/share/containers/storage:/var/lib/containers/storage \ localhost/bootc-image-builder --in-vm \ --rootfs ext4 --type raw \ quay.io/fedora/fedora-bootc:43 ``` Note: For the above to work, localhost/bootc-image-builder needs to be in the user container store.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
When running in a rootless container (made possible via osbuild/bootc-image-builder#1189) then generally the per-user container store is passed to bc-i-b, both because that makes sense, but also because the container doesn't have permissions to read the host store. This is typically done by passing
-v ~/.local/share/containers/storage:/var/lib/containers/storagewhen running bc-i-b in podman.Unfortunately when this happens, podman complains that the store is in the wrong place:
To fix this, we pass in podman arguments
--rootand--imagestoreto set up an environment where the graphroot is some empty directory that has the "correct" location and we only load the image layers from /var/lib/containers.To ensure this doesn't weirdly affect the regular case, this is all protected by podmanutil.IsRootless().