-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
There is a problem with the default location used by runsc when the --root flag is not set #6849
Comments
Hmm, this can only happen if
|
/tmp/frun.out: https://fars.ee/q6ii |
I suppose we should ignore it if the value is empty. Currently we use the bool returned by LookupEnv when we probably should just do Getenv and check if it's an empty string. Containerd checks for empty values for example: |
Fixes #6849 PiperOrigin-RevId: 413053788
Description
The --root flag is not specified by default when running runsc with podman, and the default location in https://github.com/google/gvisor/blob/master/runsc/config/flags.go#L126-L132 is found to be
/var/run/runsc
, but it actually uses the runsc folder under the relative path (the folder specified by the path of the --bundle flag when checked with sysdig)This problem still exists in the latest version (20211101)
As a side note, it is now recommended to use /run instead of /var/run
Steps to reproduce
sudo podman --cgroup-manager cgroupfs --runtime runsc --runtime-flag debug --runtime-flag debug-log=/tmp/runsc.log run --rm hello-world; grep RootDir /tmp/runsc.log
output:
runsc version
runsc version release-20211011.0
runsc debug logs (if available)
https://fars.ee/C6cG
The text was updated successfully, but these errors were encountered: