Skip to content
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

Can't execute runc command when runc in ${PATH} #35

Closed
hitsumabushi opened this issue Jun 26, 2015 · 1 comment
Closed

Can't execute runc command when runc in ${PATH} #35

hitsumabushi opened this issue Jun 26, 2015 · 1 comment

Comments

@hitsumabushi
Copy link

I can execute runc with the absolute path, however, execute runc as a command (type only "runc"), an error occur.

  1. When execute with full path

    $ sudo /usr/local/bin/runc
    / $ 
  2. When execute as a command
    /home/hitsu/work/runC is my working directory.

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
@crosbymichael
Copy link
Member

Fixed by #47

stefanberger pushed a commit to stefanberger/runc that referenced this issue Sep 8, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants