Docker Community Forums

Share and learn in the Docker community.

Pulling os-selinuxtools within machine invalidates symlinks

docker

(Jfbender) #1

I’m creating a simple docker-machine using a virtualbox driver and a rancheros.iso on my localhost. Everything goes smoothly. When I login to the new machine I perform a
#sudo ros selinux
The selinuxtools start to get pulled down but once the extraction is done I get the following errors.

ERRO[0000] symlink /usr/bin/ros /usr/bin/dockerlaunch: file exists
ERRO[0000] symlink /usr/bin/ros /usr/bin/respawn: file exists
ERRO[0000] symlink /usr/bin/ros /usr/bin/system-docker: file exists
ERRO[0000] symlink /usr/bin/ros /usr/sbin/netconf: file exists
ERRO[0000] symlink /usr/bin/ros /usr/sbin/wait-for-docker: file exists
ERRO[0000] symlink /usr/bin/ros /sbin/poweroff: file exists
ERRO[0000] symlink /usr/bin/ros /sbin/reboot: file exists
ERRO[0000] symlink /usr/bin/ros /sbin/halt: file exists
ERRO[0000] symlink /usr/bin/ros /sbin/shutdown: file exists

And all my busybox links in /usr/bin are gone. The logs in /var/log show nothing special. Any help would be great.