Skip to content

wolfi-baselayout: set /var/tmp permissions to 1777#78636

Closed
toabctl wants to merge 1 commit intowolfi-dev:mainfrom
toabctl:fix/var-tmp-permissions
Closed

wolfi-baselayout: set /var/tmp permissions to 1777#78636
toabctl wants to merge 1 commit intowolfi-dev:mainfrom
toabctl:fix/var-tmp-permissions

Conversation

@toabctl
Copy link
Member

@toabctl toabctl commented Feb 18, 2026

Summary

  • /var/tmp was being created via mkdir -p with default 0755 permissions, but every major distro (Alpine, Ubuntu, Debian, Fedora, Arch) sets it to 1777 (drwxrwxrwt), same as /tmp.
  • This was already fixed for /tmp in 0744eb9 but /var/tmp was missed.
  • The incorrect permissions caused failures in images like selenium-standalone-chromium where Xvfb uses -fbdir /var/tmp and the non-root seluser could not write to it, resulting in a cascade of failures (Xvfb → VNC → ChromeDriver → Selenium GuardedRunnable exception).

Test plan

  • Verify /var/tmp has 1777 permissions in a rebuilt image
  • Verify selenium-standalone-chromium starts without the GuardedRunnable error

Fixes: https://github.com/chainguard-dev/customer-issues/issues/3131

🤖 Generated with Claude Code

@toabctl toabctl force-pushed the fix/var-tmp-permissions branch from f9b0b88 to 7975449 Compare February 18, 2026 16:26
/var/tmp was being created via mkdir -p with default 0755 permissions.
Every major distro (Alpine, Ubuntu, Debian, Fedora, Arch) sets /var/tmp
to 1777 (drwxrwxrwt), same as /tmp, since it is a shared temporary
directory that any user should be able to write to.

This was already fixed for /tmp in 0744eb9 but /var/tmp was missed.

The incorrect permissions caused failures in images like
selenium-standalone-chromium where Xvfb uses -fbdir /var/tmp and the
non-root seluser could not write to it.

Fixes: chainguard-dev/customer-issues#3131
@toabctl toabctl force-pushed the fix/var-tmp-permissions branch from 7975449 to 1f916b5 Compare February 18, 2026 16:26
@octo-sts octo-sts bot added the bincapz/pass bincapz/pass Bincapz (aka. malcontent) scan didn't detect any CRITICALs on the scanned packages. label Feb 18, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bincapz/pass bincapz/pass Bincapz (aka. malcontent) scan didn't detect any CRITICALs on the scanned packages.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants