Asp3ctus commented 8 years ago

docker run \
  --name=zabbix-agent-xxl \
  -p 10050:10050 \
  -v /:/rootfs \
  -v /var/run:/var/run \
  -e "ZA_Server=server" \
  -e "ZA_ServerActive=server" \
  -e "ZA_StartAgents=5" \
  -e "ZA_Timeout=30" \
  -e "ZA_ListenIP=`ifconfig tun0 | grep "inet addr" | awk -F: '{print $2}' | awk '{print $1}'`" \
  -e "ZA_Hostname=$(hostname)"  \
  --net=host \
  -d --restart=always --name zabbix-agent monitoringartist/zabbix-agent-xxl-limited:latest

It starts and works but after i stop and start the container is breaking:

Zocker XXL v0.9.2b public limited version
Copyright (C) 2014-2016 Jan Garaj - www.monitoringartist.com
Freeware licence - Usage of this binary is restricted to oficial monitoringartist Docker images only.
Error #10
Zocker XXL v0.9.2b public limited version
Copyright (C) 2014-2016 Jan Garaj - www.monitoringartist.com
Freeware licence - Usage of this binary is restricted to oficial monitoringartist Docker images only.
Error #10
Zocker XXL v0.9.2b public limited version
Copyright (C) 2014-2016 Jan Garaj - www.monitoringartist.com
Freeware licence - Usage of this binary is restricted to oficial monitoringartist Docker images only.
Error #10

jangaraj commented 8 years ago

How did you restart container?

Mentat420 commented 8 years ago

I have the exact same problem (Error #10 on container restart). I've restarted my container by rebooting by computer. However, even if I just do a "docker stop zabbix-agent-xxl" followed by a "docker start zabbix-agent-xxl", I run into the same issue (Error #10). My docker run is slightly different though:

docker run \
--name=zabbixagent-xxl \
-p 10250:10050 \
-v /:/rootfs \
-v /var/run:/var/run \
-e "ZA_Server=monitoring.domain.local" \
-e "ZA_ServerActive=monitoring.domain.local" \
-h docker-agent-1 \
-d --restart=always monitoringartist/zabbix-agent-xxl-limited:latest

jangaraj commented 8 years ago

--restart=always

Unfortunately restart policy is not supported. At least not in public free image. I have idea how to fix it, but I don't want to waste my time. To be honest I don't like Docker restart policy. IMO it's should be task of your Docker orchestration.

Mentat420 commented 8 years ago

Ok. However, even if I remove the restart policy from the run command, I still run into the same issue if I do a "docker stop" followed by "docker start". Are you saying that stopping and starting the container aren't supported at all? The only way to use this is removing the container and rebuilding it each time? (Just trying to confirm)

Thanks!

jangaraj commented 8 years ago

docker stop + docker start = docker restart = --restart=always = still the same problem. Yes, you need to remove old zabbix-agent container and start new one in your case. Container is stateless, so it's not a problem.

suhsteve commented 8 years ago

Does this mean that if a machine reboots, we will have to remove the zabbix-agent container and start a new one every time ?

jangaraj commented 8 years ago

Yes, you have to remove the zabbix-agent container and start a new one every time. I recommend to use it as a systemd service, so you can create service "hook" which will remove container before start.