Rtnetlink Answers: No Such File or Directory

Docker: Running container from CLI fails but not from docker desktop, RTENETLINK Oper not permitted

Launching the container for the same image from the command line doesn't fail, if you look at the logs of the container that you started with Docker Desktop you'll see the same lines.

What happens is that the centos dockerfile use bash as its default command.

When you run a container it will attach to stdout and stderr by default but not stdin.

adding -i will attach stdin.

adding -t will provide you with a pseudo-tty

To actually use bash you'll need to provide both : -it

To sum up, here's how to mimick what Docker Desktop does, starting the container in the background with -d:

docker run -it -d ghcr.io/nokia/srlinux

RTNETLINK answers: Invalid argument, MPLS on mininet

I solved my problem by changing the value on /proc/sys/net/mpls/platform_labels the value set here will be the highest label value that can be used

But keep in mind that I have to set this value for all the devices on my mininet network as well as loading the mpls module and any parameter

* modprobe mpls_router
* modprobe mpls_gso
* modprobe mpls_iptunnel
* sysctl -w net.mpls.platform_labels=1048575
* sysctl -w net.mpls.conf.*-eth#.input=1 #for every interface that speaks mpls

I thought that doing it in it kernel will activate it for all, but apparently it has to be done within every device on the network



Related Topics



Leave a reply



Submit