Skip to content

feat(docker): build and publish unprivileged Docker image #10485

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

sgaist
Copy link

@sgaist sgaist commented Jun 5, 2025

Description

This PR:

  • adds a new Dockerfile that will build from the nginx unprivileged image
  • modify the pipeline so that it builds images for both standard and unprivileged images

Similar to swagger-api/swagger-editor#3705

Motivation and Context

This will allow to deploy Swagger-UI on clusters such as OpenShift without having to meddle with the security context and security context constraints.

Fixes #10254

How Has This Been Tested?

  • Manual build of the Dockerfile.unprivileged image is successful
  • Starting a container using this image is successful
  • Starting a container using this image with a different user is successful
  • No error logged during the startup

Checklist

My PR contains...

  • No code changes (src/ is unmodified: changes to documentation, CI, metadata, etc.)
  • [] Dependency changes (any modification to dependencies in package.json)
  • [] Bug fixes (non-breaking change which fixes an issue)
  • [] Improvements (misc. changes to existing features)
  • Features (non-breaking change which adds functionality)

My changes...

  • are breaking changes to a public API (config options, System API, major UI change, etc).
  • are breaking changes to a private API (Redux, component props, utility functions, etc.).
  • are breaking changes to a developer API (npm script behavior changes, new dev system dependencies, etc).
  • are not breaking changes.

Documentation

  • My changes do not require a change to the project documentation.
  • My changes require a change to the project documentation.
  • If yes to above: I have updated the documentation accordingly.

Automated tests

  • My changes can not or do not need to be tested.
  • My changes can and should be tested by unit and/or integration tests.
  • If yes to above: I have added tests to cover my changes.
  • If yes to above: I have taken care to cover edge cases in my tests.
  • All new and existing tests passed.

Similar to swagger-editor

This will allow to deploy Swagger-UI on clusters such as
OpenShift without having to meddle with the security
context and security context constraints.
@sgaist sgaist force-pushed the ft/10254-add-unprivileged-image branch from 8bd57e4 to 9d6967f Compare June 5, 2025 12:14
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.

Publish nginxinc/nginx-unprivileged based image
1 participant