Skip to content

chroot: error out on --network != host when $BUILDAH_ISOLATION#6697

Open
nalind wants to merge 1 commit intocontainers:mainfrom
nalind:isolation-env
Open

chroot: error out on --network != host when $BUILDAH_ISOLATION#6697
nalind wants to merge 1 commit intocontainers:mainfrom
nalind:isolation-env

Conversation

@nalind
Copy link
Member

@nalind nalind commented Feb 23, 2026

What type of PR is this?

/kind bug

What this PR does / why we need it:

Error out if someone tries to mix the --network CLI flag, with a value other than "host", with chroot isolation configured by setting $BUILDAH_ISOLATION to "chroot", as we have been doing for cases where it's done using the "--isolation" option, instead of just ignoring it as we did previously.

How to verify it

Updated integration test!

Which issue(s) this PR fixes:

Fixes #6696

Special notes for your reviewer:

Does this PR introduce a user-facing change?

Attempting to use the `--network` option with a value other than "host" when "BUILDAH_ISOLATION" is set to "chroot" in the environment now produces an error, as it would with `--isolation=chroot`.

@dosubot dosubot bot added the size:XS This PR changes 0-9 lines, ignoring generated files. label Feb 23, 2026
Error out if someone tries to mix the --network CLI flag, with a value
other than "host", with chroot isolation configured by setting
$BUILDAH_ISOLATION to "chroot", as we have been doing for cases where
it's done using the "--isolation" option, instead of just ignoring it as
we did previously.

Signed-off-by: Nalin Dahyabhai <nalin@redhat.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

size:XS This PR changes 0-9 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

--network conflicts with --isolation=chroot, but not with BUILDAH_ISOLATION=chroot

1 participant