Skip to content

Resolve seccomp profile on bin/up and bin/upgrade - #441

Open
mserranom wants to merge 1 commit into
mle-podman-supportfrom
msm-seccomp-resolution
Open

Resolve seccomp profile on bin/up and bin/upgrade#441
mserranom wants to merge 1 commit into
mle-podman-supportfrom
msm-seccomp-resolution

Conversation

@mserranom

@mserranom mserranom commented Aug 26, 2026

Copy link
Copy Markdown
Contributor

Description

Adds resolution of seccomp profile in bin/up and bin/upgrade scripts.

  • Added extract_seccomp_profile_from_image to shared_functions, which is used in bin/podman_setup.
  • Added ensure_seccomp_profile to shared_functions. Performs the relevant checks (SP + Sibling Containers + podman) before extracting the profile.
  • Added ensure_seccomp_profile to bin/up and bin/upgrade scripts.
  • bin/doctor: the seccomp check block is now gated on SERVER_PRO=true && SIBLING_CONTAINERS_ENABLED=true, matching the SELinux gate right above it.

Related issues / Pull Requests

Contributor Agreement

@mserranom

Copy link
Copy Markdown
Contributor Author

@mlevans0 to be merged in your branch - #441

Comment thread bin/up
if [[ $SERVER_PRO == "true" && "$SIBLING_CONTAINERS_ENABLED" == "true" ]]; then
pull_sandboxed_compiles
set_server_pro_image_name "$IMAGE_VERSION"
ensure_seccomp_profile || true

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure about this, should we print the warnings and let the user continue with the setup, or halt here?
Cc @mlevans0

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

My thinking was that for any of the hardening types of changes we’d just let the container start even though it wouldn’t work as it would help with debugging for their modules/policies. A non working container allows the customer to click around and trigger events to fix.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cool, let's keep it as it is then, and revisit once we have further feedback.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants