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

cannot start labs (execve: Bad address) #11

Closed
edipascale opened this issue Jun 18, 2018 · 3 comments
Closed

cannot start labs (execve: Bad address) #11

edipascale opened this issue Jun 18, 2018 · 3 comments

Comments

@edipascale
Copy link

On Ubuntu 18.04 with Kathara 0.30, after installing Kathara as per the instructions in the README, whenever I try to run a command such as $NETKIT_HOME/lstart or $NETKIT_HOME/lclean I only get a sequence of

-1
execve: Bad address
-1
execve: Bad address
[...]

I tried this both with the maracas example suggested in the README and the single swith P4 example in included with the source.

@glospoto
Copy link
Member

Hi @manuhalo , please, can you try to bypass the wrapper, by installing Kathara with the option --admin? This implies to use sudo to run Kathara, so do that if and only if your user is part of the sudo group. Thanks.

@edipascale
Copy link
Author

Thanks @glospoto, this removed the bad address issue, but now it's complaining that it can't start the containers:

========================= Starting Lab ==========================
[sudo] password for emanuele: 
Error response from daemon: No such container: netkit_1000_host
Error response from daemon: No such container: netkit_1000_server
Error response from daemon: No such container: netkit_1000_rip2
Error response from daemon: No such container: netkit_1000_rip1
Error response from daemon: No such container: netkit_1000_br
Error response from daemon: No such container: netkit_1000_ospf1
Error response from daemon: No such container: netkit_1000_ospf3
Error response from daemon: No such container: netkit_1000_ospf2
Error: failed to start containers: netkit_1000_host, netkit_1000_server, netkit_1000_rip2, netkit_1000_rip1, netkit_1000_br, netkit_1000_ospf1, netkit_1000_ospf3, netkit_1000_ospf2
Error: No such container: netkit_1000_ospf2
[...]

Also docker container ls shows nothing. Just in case it's a version problem:

$ docker --version
Docker version 17.12.1-ce, build 7390fc6
$ docker images 
REPOSITORY                   TAG                 IMAGE ID            CREATED             SIZE
kathara/p4                   latest              b9d3bfcbf4d1        3 weeks ago         14.4GB
kathara/netkit_base          latest              84dd1b266768        3 weeks ago         803MB
petergrace/opentsdb-docker   latest              cf661f5f02a7        3 weeks ago         537MB

@Kidel
Copy link
Member

Kidel commented Jun 20, 2018

That is because the system thinks you already started the containers and is trying to restart them instead of creating them.

Try to run $NETKIT_HOME/lwipe and $NETKIT_HOME/lstart

or simply $NETKIT_HOME/lrestart

@Kidel Kidel closed this as completed Jun 20, 2018
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

3 participants