I have installed rancheros v0.4.4 to disk inside a Virtualbox VM using
sudo ros install -c cloud_config.yml -d /dev/sda
my cloud-config.yml file contains my ssh public key and hostname
I can ssh into the vm and the hostname is properly set, however when I run docker ps I get the following error
Cannot connect to the Docker daemon. Is the docker daemon running on this host?
sudo system-docker ps works as expected.
I have tried searching for this error and the only result I found was related to rancheros v.03.3 and the only response was to check if system-docker was running.
Is there a way I can start the docker daemon on the vm?
as additional information, all the above commands work properly and the docker daemon is running if I do the install on hardware. This must be a problem with either virtualbox or my setup of the vm.
Dave
Have you tried restarting the VM? I install using virtualbox and have seen this happen once, but am unable to consistently reproduce.
In sudo system-docker ps -a, do you see the docker container as exited?
I get the message that docker is restarting
f018d7e04db7 rancher/os-network:v0.4.4 “/usr/sbin/entry.sh w” 3 hours ago Exited (0) 8 minutes ago wait-for-network
7362fedca6ee rancher/os-docker:v0.4.4 “/usr/sbin/entry.sh /” 3 hours ago Restarting (0) About a minute ago docker
47b6fea9df77 rancher/os-network:v0.4.4 “/usr/sbin/entry.sh /” 3 hours ago Up 7 minutes network
i did a logs -f on the container and it is repeating theses lines
time=“2016-05-02T17:38:55Z” level=info msg="Running [/usr/sbin/docker-init daemon --log-opt max-size=25m --log-opt max-file=2 -s overlay -G docker -H unix:///var/run/docker.sock]"
time=“2016-05-02T17:42:20Z” level=info msg="Starting Docker in context: console"
time=“2016-05-02T17:42:20Z” level=info msg="Getting PID for service: console"
time=“2016-05-02T17:42:20Z” level=info msg="console PID 605"
time=“2016-05-02T17:42:20Z” level=info msg="Docker PID 1097"
time=“2016-05-02T17:42:20Z” level=info msg="Moving Docker to cgroup /host/sys/fs/cgroup/systemd/docker/55fbc62d79b6c569e674fc992be2724ebbdd41995361d11150bc651863833663"
time=“2016-05-02T17:42:20Z” level=info msg="Moving Docker to cgroup /host/sys/fs/cgroup/cpu,cpuacct/docker/55fbc62d79b6c569e674fc992be2724ebbdd41995361d11150bc651863833663"
time=“2016-05-02T17:42:20Z” level=info msg="Moving Docker to cgroup /host/sys/fs/cgroup/cpuset/docker/55fbc62d79b6c569e674fc992be2724ebbdd41995361d11150bc651863833663"
time=“2016-05-02T17:42:20Z” level=info msg="Moving Docker to cgroup /host/sys/fs/cgroup/perf_event/docker/55fbc62d79b6c569e674fc992be2724ebbdd41995361d11150bc651863833663"
time=“2016-05-02T17:42:20Z” level=info msg="Moving Docker to cgroup /host/sys/fs/cgroup/net_cls,net_prio/docker/55fbc62d79b6c569e674fc992be2724ebbdd41995361d11150bc651863833663"
time=“2016-05-02T17:42:20Z” level=info msg="Moving Docker to cgroup /host/sys/fs/cgroup/freezer/docker/55fbc62d79b6c569e674fc992be2724ebbdd41995361d11150bc651863833663"
time=“2016-05-02T17:42:20Z” level=info msg="Moving Docker to cgroup /host/sys/fs/cgroup/devices/docker/55fbc62d79b6c569e674fc992be2724ebbdd41995361d11150bc651863833663"
time=“2016-05-02T17:42:20Z” level=info msg="Moving Docker to cgroup /host/sys/fs/cgroup/memory/docker/55fbc62d79b6c569e674fc992be2724ebbdd41995361d11150bc651863833663"
time=“2016-05-02T17:42:20Z” level=info msg="Moving Docker to cgroup /host/sys/fs/cgroup/blkio/docker/55fbc62d79b6c569e674fc992be2724ebbdd41995361d11150bc651863833663"
time=“2016-05-02T17:42:20Z” level=info msg=“Running [/usr/sbin/docker-init daemon --log-opt max-size=25m --log-opt max-file=2 -s overlay -G docker -H unix:///var/run/docker.sock]”
Can you consistently reproduce it? As I mentioned earlier, I’ve only seen this once, so want to see if you have this issue consistently.
We’ve recently released v0.4.5, so you could try our latest release as well.
Hello
I have the same problem with a fresh install of rancherOS 0.4.5 within Hyper-V.
sudo system-docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
9b17f85a9e7c rancher/os-docker:v0.4.5 “/usr/sbin/entry.sh /” 2 hours ago Restarting (0) 17 seconds ago docker
ad0fc1115bbc rancher/os-console:v0.4.5 “/usr/sbin/entry.sh r” 2 hours ago Exited (137) 2 hours ago reboot
bd14db0e6fd3 docker “docker-entrypoint.sh” 2 hours ago Exited (0) 2 hours ago hungry_brahmagupta
cda673d032d4 rancher/os-console:v0.4.5 “/usr/sbin/entry.sh s” 7 hours ago Exited (137) 7 hours ago shutdown
826dd5bddb0a rancher/os-preload:v0.4.5 “/usr/sbin/entry.sh /” 7 hours ago Exited (0) 2 hours ago preload-user-images
2e2ec1809e29 rancher/os-console:v0.4.5 “/usr/sbin/entry.sh /” 7 hours ago Up 2 hours console
227a926778fe rancher/os-network:v0.4.5 “/usr/sbin/entry.sh w” 7 hours ago Exited (0) 2 hours ago wait-for-network
6ce697c31575 rancher/os-network:v0.4.5 “/usr/sbin/entry.sh /” 7 hours ago Up 2 hours network
c85285a79f1a rancher/os-cloudinit:v0.4.5 “/usr/sbin/entry.sh /” 7 hours ago Exited (0) 2 hours ago cloud-init
96cc62946bfc rancher/os-ntp:v0.4.5 “/usr/sbin/entry.sh /” 7 hours ago Up 2 hours ntp
da0cc317e834 rancher/os-network:v0.4.5 “/usr/sbin/entry.sh w” 7 hours ago Exited (0) 2 hours ago wait-for-network-pre
1160e6ba503c rancher/os-network:v0.4.5 “/usr/sbin/entry.sh /” 7 hours ago Exited (0) 2 hours ago network-pre
5615ca636e22 rancher/os-udev:v0.4.5 “/usr/sbin/entry.sh /” 7 hours ago Up 2 hours udev
3b74850d5be5 rancher/os-cloudinit:v0.4.5 “/usr/sbin/entry.sh /” 7 hours ago Exited (0) 2 hours ago cloud-init-pre
02d2b6c17949 rancher/os-state:v0.4.5 “/usr/sbin/entry.sh e” 7 hours ago Created all-volumes
70aca0548c5e rancher/os-preload:v0.4.5 “/usr/sbin/entry.sh /” 7 hours ago Exited (0) 2 hours ago preload-system-images
cc16182f8616 rancher/os-acpid:v0.4.5 “/usr/sbin/entry.sh /” 7 hours ago Up 2 hours acpid
d9af5b3d2acb rancher/os-udev:v0.4.5 “/usr/sbin/entry.sh /” 7 hours ago Exited (0) 2 hours ago udev-cold
04e3422c4731 rancher/os-syslog:v0.4.5 “/usr/sbin/entry.sh /” 7 hours ago Up 2 hours syslog
470a6f3d2a03 rancher/os-state:v0.4.5 “/usr/sbin/entry.sh e” 7 hours ago Created user-volumes
fa64f5e68b15 rancher/os-state:v0.4.5 “/usr/sbin/entry.sh e” 7 hours ago Created container-data-volumes
f11b8a2c88f9 rancher/os-state:v0.4.5 “/usr/sbin/entry.sh e” 7 hours ago Created system-volumes
9edd47df4186 rancher/os-state:v0.4.5 “/usr/sbin/entry.sh e” 7 hours ago Created command-volumes
It keeps constantly restarting after a system reboot.
sudo system-docker logs docker shows this:
time=“2016-06-07T16:18:53Z” level=info msg="Starting Docker in context: console"
time=“2016-06-07T16:18:53Z” level=info msg="Getting PID for service: console"
time=“2016-06-07T16:18:53Z” level=info msg="console PID 541"
time=“2016-06-07T16:18:53Z” level=info msg="Docker PID 1564"
time=“2016-06-07T16:18:53Z” level=info msg="Moving Docker to cgroup /host/sys/fs/cgroup/systemd/docker/2e2ec1809e292c3df46f23e8178f931435b8b504c3b6d4164728b8e695829506"
time=“2016-06-07T16:18:53Z” level=info msg="Moving Docker to cgroup /host/sys/fs/cgroup/net_cls,net_prio/docker/2e2ec1809e292c3df46f23e8178f931435b8b504c3b6d4164728b8e695829506"
time=“2016-06-07T16:18:53Z” level=info msg="Moving Docker to cgroup /host/sys/fs/cgroup/freezer/docker/2e2ec1809e292c3df46f23e8178f931435b8b504c3b6d4164728b8e695829506"
time=“2016-06-07T16:18:53Z” level=info msg="Moving Docker to cgroup /host/sys/fs/cgroup/devices/docker/2e2ec1809e292c3df46f23e8178f931435b8b504c3b6d4164728b8e695829506"
time=“2016-06-07T16:18:53Z” level=info msg="Moving Docker to cgroup /host/sys/fs/cgroup/memory/docker/2e2ec1809e292c3df46f23e8178f931435b8b504c3b6d4164728b8e695829506"
time=“2016-06-07T16:18:53Z” level=info msg="Moving Docker to cgroup /host/sys/fs/cgroup/blkio/docker/2e2ec1809e292c3df46f23e8178f931435b8b504c3b6d4164728b8e695829506"
time=“2016-06-07T16:18:53Z” level=info msg="Moving Docker to cgroup /host/sys/fs/cgroup/cpu,cpuacct/docker/2e2ec1809e292c3df46f23e8178f931435b8b504c3b6d4164728b8e695829506"
time=“2016-06-07T16:18:53Z” level=info msg="Moving Docker to cgroup /host/sys/fs/cgroup/cpuset/docker/2e2ec1809e292c3df46f23e8178f931435b8b504c3b6d4164728b8e695829506"
time=“2016-06-07T16:18:53Z” level=info msg="Moving Docker to cgroup /host/sys/fs/cgroup/perf_event/docker/2e2ec1809e292c3df46f23e8178f931435b8b504c3b6d4164728b8e695829506"
time=“2016-06-07T16:18:53Z” level=info msg=“Running [/usr/sbin/docker-init daemon --log-opt max-size=25m --log-opt max-file=2 -s overlay -G docker -H unix:///var/run/docker.sock]”
The Docker container was running fine until i rebooted the system. I installed the rancher/server and the rancher/agent before rebooting. These were working fine.
I tried to remove the OS-Docker with sudo system-docker rm -f ID and reinstall it via ros os upgrade, but that didnt work. It still keeps restarting.
Problem solved: It was because I changed the password of the “rancher” account right after writing RancherOS to the disk.