We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I can execute runc with the absolute path, however, execute runc as a command (type only "runc"), an error occur.
When execute with full path
$ sudo /usr/local/bin/runc / $
When execute as a command /home/hitsu/work/runC is my working directory.
/home/hitsu/work/runC
sudo runc Timestamp: 2015-06-26 09:09:39.184956634 +0900 JST Code: System error Message: fork/exec /home/hitsu/work/runC/runc: no such file or directory Frames: --- 0: start Package: github.com/opencontainers/runc/libcontainer.(*initProcess) File: process_linux.go@183 --- 1: Start Package: github.com/opencontainers/runc/libcontainer.(*linuxContainer) File: container_linux.go@107 --- 2: execContainer Package: main File: run.go@41 --- 3: func·006 Package: main File: main.go@89 --- 4: Run Package: github.com/codegangsta/cli.(*App) File: app.go@159 --- 5: main Package: main File: main.go@104 --- 6: main Package: runtime File: proc.go@63 --- 7: goexit Package: runtime File: asm_amd64.s@2232
The text was updated successfully, but these errors were encountered:
allow to exec as command. See opencontainers#35
f5d4dc0
Fixed by #47
Sorry, something went wrong.
Merge pull request opencontainers#35 from mrunalp/rlimits
aa7e143
Adds section for Linux Rlimits
No branches or pull requests
I can execute runc with the absolute path, however, execute runc as a command (type only "runc"), an error occur.
When execute with full path
When execute as a command
/home/hitsu/work/runC
is my working directory.The text was updated successfully, but these errors were encountered: