opscenter container status exited (1) after 10 sec

[prott8gf]

Hi,

for some reason the opscenter image won't Start. Im using the guide provider in the repository... After 10 sec it throws the exit code 1. It seems Mike nothing happens cause the container dies not Grab an ip.

Tested with the april 2015 poklet/opscenter build on:
Ubuntu 14.04.02 - docker 1.0.1
Ubuntu 15.04 - docker 1.5

CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
9f96ccc5da48 poklet/opscenter:latest /bin/sh -c start 3 minutes ago Exited (1) 3 minutes ago ops

Starting OpsCenter on 172.17.0.2...
/usr/local/bin/start: line 8: service: command not found
tail: cannot open '/var/log/opscenter/opscenterd.log' for reading: No such file or directory
tail: no files remaining

is there a quick solution?

Kind regards

[prott8gf]

Cloud there be an error in the config of the image?

[{
"Args": [
"-c",
"start"
],
"Config": {
"AttachStderr": false,
"AttachStdin": false,
"AttachStdout": false,
"Cmd": [
"/bin/sh",
"-c",
"start"
],
"CpuShares": 0,
"Cpuset": "",
"Domainname": "",
"Entrypoint": null,
"Env": [
"PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"
],
"ExposedPorts": {
"50031/tcp": {},
"61620/tcp": {},
"8888/tcp": {}
},
"Hostname": "9f96ccc5da48",
"Image": "poklet/opscenter",
"Memory": 0,
"MemorySwap": 0,
"NetworkDisabled": false,
"OnBuild": null,
"OpenStdin": false,
"PortSpecs": null,
"StdinOnce": false,
"Tty": false,
"User": "root",
"Volumes": null,
"WorkingDir": ""
},
"Created": "2015-04-30T11:21:06.665715822Z",
"Driver": "aufs",
"ExecDriver": "native-0.2",
"HostConfig": {
"Binds": null,
"ContainerIDFile": "",
"Dns": null,
"DnsSearch": null,
"Links": null,
"LxcConf": [],
"NetworkMode": "bridge",
"PortBindings": {
"50031/tcp": null,
"61620/tcp": null,
"8888/tcp": null
},
"Privileged": false,
"PublishAllPorts": false,
"VolumesFrom": null
},
"HostnamePath": "/var/lib/docker/containers/9f96ccc5da485f41fd74097a70f333a0bd2b7d551d2a045f5a3667000b4ad585/hostname",
"HostsPath": "/var/lib/docker/containers/9f96ccc5da485f41fd74097a70f333a0bd2b7d551d2a045f5a3667000b4ad585/hosts",
"Id": "9f96ccc5da485f41fd74097a70f333a0bd2b7d551d2a045f5a3667000b4ad585",
"Image": "6bcd181ef99a9f62e0abecc0bad17d5246028f19b2d0e5ef3b1b249c76f8082c",
"MountLabel": "",
"Name": "/ops",
"NetworkSettings": {
"Bridge": "",
"Gateway": "",
"IPAddress": "",
"IPPrefixLen": 0,
"PortMapping": null,
"Ports": null
},
"Path": "/bin/sh",
"ProcessLabel": "",
"ResolvConfPath": "/etc/resolv.conf",
"State": {
"ExitCode": 1,
"FinishedAt": "2015-04-30T11:33:34.112779217Z",
"Paused": false,
"Pid": 0,
"Running": false,
"StartedAt": "2015-04-30T11:33:34.057475087Z"
},
"Volumes": {},
"VolumesRW": {}
}

[pokle]

The logs give a very strange clue. It's as if the 'service' command has gone missing.

/usr/local/bin/start: line 8: service: command not found

I'll try and reproduce it on my computer.

[etspaceman]

I'm seeing this issue too. Exact same problem. Any updates here?

[malteseduck]

Maybe because the centos7 docker image uses fakesystemd instead of systemd:

https://groups.google.com/forum/#!topic/docker-user/ebCUAGNuO44
http://jperrin.github.io/centos/2014/09/25/centos-docker-and-systemd/
http://developerblog.redhat.com/2014/05/05/running-systemd-within-docker-container/

Not a problem in the centos6 image. Does the opscenter require centos7, or could 6 be used? Or maybe use supervisord instead?

http://supervisord.org/

Maybe not, but options.

[malteseduck]

Changing the DockerFile so it is using centos6 seems to work fine, except I had to also omit the line that installed hostname. Is there something in the opscenter that requires this be available?

So, a "quick" workaround is to use centos6. Maybe not the best, but I have a local image running that seems to be working.