diff options
| author | jbsky <webmaster@jbsky.fr> | 2026-10-06 04:38:13 +0000 |
|---|---|---|
| committer | jbsky <webmaster@jbsky.fr> | 2026-10-06 04:38:13 +0000 |
| commit | e06e71a04d1b4717d6a78060924112cbf68e0fe3 (patch) | |
| tree | b18f6514010f2f51fcca87deeb36b5c4de87e5ed /src/migration-scripts | |
| parent | 87e0a46281746f92a0dde4c7d71c86aa00ec90ea (diff) | |
| download | vyos-1x-e06e71a04d1b4717d6a78060924112cbf68e0fe3.tar.gz vyos-1x-e06e71a04d1b4717d6a78060924112cbf68e0fe3.zip | |
container: T9401: add chown option to tmpfs mounts
Since T9024 (Podman 5.8.4, crun replaced by runc 1.1.5), a tmpfs mounted
over a directory that already exists in the image is owned by root:root
0755, whatever the image prepared. A container running as a non-root
user (image USER or uid/gid) can no longer write its pid file or control
socket there and fails to start. With crun 1.8.1 every tmpfs was 1777,
so the same configuration used to work.
runc 1.1.5 ignores tmpfs-mode; the Podman mount option `U` (chown the
mount to the container user) is the only one that works on the runtime
VyOS ships. Expose it as a valueless `chown` node:
set container name <name> tmpfs <tag> chown
Without the option the generated Quadlet line is unchanged.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Diffstat (limited to 'src/migration-scripts')
0 files changed, 0 insertions, 0 deletions
