Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • abuild abuild
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 56
    • Issues 56
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 31
    • Merge requests 31
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • alpinealpine
  • abuildabuild
  • Merge requests
  • !179

abuild-rootbld: clear environment for bwrap container

  • Review changes

  • Download
  • Email patches
  • Plain diff
Open Sören Tempel requested to merge nmeum/abuild:rootbld-clearenv into master Jan 21, 2023
  • Overview 2
  • Commits 1
  • Pipelines 0
  • Changes 1

Otherwise, user-set environment variables can leak into the container and cause spurious build/test failures. A common example is the value of the SHELL environment variable which is used by a lot of software. Outside of the bwrap container I use ksh and my SHELL environment variable points to /bin/ksh, however, inside the container /bin/ksh is not available and hence software relying on $SHELL doesn't work properly. This can cause annoying to debug test failures, e.g. aports!43430 (merged).

Edited Jan 21, 2023 by Sören Tempel
Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: rootbld-clearenv