Docker image fails when run as a non-root user #1
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The Tokai image cannot start under a non-root Kubernetes security context.
uv run --no-sync initializes its cache at /.cache/uv, but the image filesystem is root-owned. When the container runs as a non-root user, startup fails:
This prevents deployments using a restricted/non-root pod security policy unless an extra writable volume is mounted at /.cache.
Expected behavior
The image should support running as an arbitrary non-root user without requiring a root-owned filesystem path to be writable.
Suggested fix
Configure uv’s cache to use a universally writable location such as /tmp/uv-cache, or create and use a non-root user with a writable home/cache directory in the Docker image.