Error in starting
alessioguglielmo opened this issue · comments
docker run -d --net host --name docker-discover -e ETCD_HOST=192.168.56.102:4001 -p 1936:1936 -t jwilder/docker-discover
docker logs docker-discover
Error: 'Key not found : /backends'
Error: 'Key not found : /backends'
Error: 'Key not found : /backends'
Error: 'Key not found : /backends'
service on 1936 is unreacheable. Also whoami servers is unreacheable.
If I try to connect directly to a single whoami serv it works fine.
Solved adding '--privileged' option to run command... :( dangerous?!?
What version of docker and host OS are you using?
I'm using Docker 1.2.0 on Fedora20 hosts (5 instances) installed on VirtualBox.
In instance num.1 I've installed Ansible-Docker in order to implement container orchestration across multiple hosts.
Could privileged containers in multi-tenant environment expose to privilege escalation the underlying host?
I would build a scenario for load-balanced website that can accept public request from external network. How can I change ' --net host ' ??
thanks for your tutorial. It's great
From you're original issues (permission denied), this might be related SELinux. nginx-proxy/nginx-proxy#40 had a similar problem that seems to be caused by SELinux.
I run
yum upgrade selinux-policy && reboot on backend hosts to fix it but seems that without --privilege' option containers don't work... (I disabled SELinux on other nodes because I've found problem)
I think either --privilege or using docker 1.3 --security-opt to set SELinux labels might be the way to fix this. I'm not sure what SELinux labels would be required at the moment.
Ok, I will try.
It works with --privileged