Installing on Intel NUC not working: it stops and show no progress.
Closed this issue · 7 comments
I have Ubuntu 18.04.1 LTS on Intel NUC7i3BNK.
When I want to install databox, it doesn't show progress.
The output:
dbnuc@dbnuc:~/databox$ docker run --rm -v /var/run/docker.sock:/var/run/docker.sock -v $(pwd)/certs:/certs -v $(pwd)/sdk:/sdk -v -t databoxsystems/databox:latest /databox start --host-path $(pwd) -sslHostName $(hostname)
Unable to find image 'databoxsystems/databox:latest' locally
latest: Pulling from databoxsystems/databox
4fe2ade4980c: Pull complete
a00b0249c0bf: Pull complete
ef3d9ec49d75: Pull complete
945129d14a01: Pull complete
Digest: sha256:0db03f2632f112a06c7a3a835d1e97a2d2e9f62db4bea4c46e3e4a175995240c
Status: Downloaded newer image for databoxsystems/databox:latest
[INFO]2018/10/02 12:41:47 Starting Databox 0.5.0
[INFO]2018/10/02 12:41:47 Pulling Image databoxsystems/container-manager-amd64:0.5.0
[INFO]2018/10/02 12:41:51 Done pulling Image databoxsystems/container-manager-amd64:0.5.0
[INFO]2018/10/02 12:41:51 Outputting logs
and the output of docekr service ls
:
dbnuc@dbnuc:~$ docker service ls
ID NAME MODE REPLICAS IMAGE PORTS
2x0olzkk5yif container-manager replicated 0/1 databoxsystems/container-manager-amd64:0.5.0
dbnuc@dbnuc:~$
Internet : eduroam at Imperial.
whats the output of
docker service logs container-manager
you can also add -v to the start command to get more debug output
Using start -v
:
dbnuc@dbnuc:~$ docker run --rm -v /var/run/docker.sock:/var/run/docker.sock -v $(pwd)/certs:/certs -v $(pwd)/sdk:/sdk -v -t databoxsystems/databox:latest /databox start -v --host-path $(pwd) -sslHostName $(hostname)
Unable to find image 'databoxsystems/databox:latest' locally
latest: Pulling from databoxsystems/databox
4fe2ade4980c: Pull complete
a00b0249c0bf: Pull complete
ef3d9ec49d75: Pull complete
945129d14a01: Pull complete
Digest: sha256:0db03f2632f112a06c7a3a835d1e97a2d2e9f62db4bea4c46e3e4a175995240c
Status: Downloaded newer image for databoxsystems/databox:latest
[INFO]2018/10/02 13:21:32 Starting Databox 0.5.0
[INFO]2018/10/02 13:21:32 Pulling Image databoxsystems/container-manager-amd64:0.5.0
[INFO]2018/10/02 13:21:35 Done pulling Image databoxsystems/container-manager-amd64:0.5.0
[INFO]2018/10/02 13:21:35 Outputting logs
output of docker service logs container-manager
shows nothing ( debug is true) .
if service logs container-manager is blank, it usually means docker can't find the image.
is databoxsystems/container-manager-amd64:0.5.0 in
docker images
you might get some more information from docker events
run it in a separate terminal before starting databox
also, it might be worth trying a docker pull databoxsystems/databox:latest
its a multiformat image and sometimes docker does not pull the latest version properly.
is databoxsystems/container-manager-amd64:0.5.0 in
docker images
Yes, this is the output ofdocker images
dbnuc@dbnuc:~$ docker images
REPOSITORY TAG IMAGE ID CREATED SIZE
databoxsystems/databox latest 7b58ce4bdf21 2 weeks ago 15.1MB
databoxsystems/container-manager-amd64 0.5.0 05e7dd537254 6 weeks ago 15.8MB
dbnuc@dbnuc:~$
docker events
continuously prints this message, every second:
2018-10-03T14:31:33.981460239+01:00 container destroy 3540ea5ea8b64bc6493934af95dd34aea6e8aa8eb68a1761568ace1cfd0c1793 (com.docker.swarm.node.id=bj5yoqh3j397w4nrcpkhox2ks, com.docker.swarm.service.id=vt42swdvr10wk7jywa4j3zrhe, com.docker.swarm.service.name=container-manager, com.docker.swarm.task=, com.docker.swarm.task.id=bhm18gkza5etstvc3x85zuyhy, com.docker.swarm.task.name=container-manager.1.bhm18gkza5etstvc3x85zuyhy, databox.type=container-manager, image=databoxsystems/container-manager-amd64:0.5.0, name=container-manager.1.bhm18gkza5etstvc3x85zuyhy)
2018-10-03T14:31:34.979287825+01:00 image pull databoxsystems/container-manager-amd64:0.5.0 (databox.type=container-manager, name=databoxsystems/container-manager-amd64)
2018-10-03T14:31:35.068918177+01:00 container create 4a5d5370d1bf5b75adffd7d8ebee5ac0a9a0457e88b20b76d31603c87943f762 (com.docker.swarm.node.id=bj5yoqh3j397w4nrcpkhox2ks, com.docker.swarm.service.id=vt42swdvr10wk7jywa4j3zrhe, com.docker.swarm.service.name=container-manager, com.docker.swarm.task=, com.docker.swarm.task.id=okkrb2wexm4h1v5b3tsndvy4z, com.docker.swarm.task.name=container-manager.1.okkrb2wexm4h1v5b3tsndvy4z, databox.type=container-manager, image=databoxsystems/container-manager-amd64:0.5.0, name=container-manager.1.okkrb2wexm4h1v5b3tsndvy4z)
2018-10-03T14:31:38.882373732+01:00 network disconnect 687f694425a57d32592e1c98f76ac2239d55811d246fb5f47ea7276b1cc882a0 (container=4a5d5370d1bf5b75adffd7d8ebee5ac0a9a0457e88b20b76d31603c87943f762, name=bridge, type=bridge)
2018-10-03T14:31:39.349181095+01:00 container destroy d1c07d1975eb8893ca0ed865c1ea52c506952dc6eef630d9387fe4ca0aad7a0f (com.docker.swarm.node.id=bj5yoqh3j397w4nrcpkhox2ks, com.docker.swarm.service.id=vt42swdvr10wk7jywa4j3zrhe, com.docker.swarm.service.name=container-manager, com.docker.swarm.task=, com.docker.swarm.task.id=42uszlqyzcrbcg3u2b3s99qg2, com.docker.swarm.task.name=container-manager.1.42uszlqyzcrbcg3u2b3s99qg2, databox.type=container-manager, image=databoxsystems/container-manager-amd64:0.5.0, name=container-manager.1.42uszlqyzcrbcg3u2b3s99qg2)
2018-10-03T14:31:40.231663491+01:00 image pull databoxsystems/container-manager-amd64:0.5.0 (databox.type=container-manager, name=databoxsystems/container-manager-amd64)
2018-10-03T14:31:40.345297721+01:00 container create 69911ed152fe773a1f99fa890fae647c0fc17da1022909ad1dd99427ce71b5c3 (com.docker.swarm.node.id=bj5yoqh3j397w4nrcpkhox2ks, com.docker.swarm.service.id=vt42swdvr10wk7jywa4j3zrhe, com.docker.swarm.service.name=container-manager, com.docker.swarm.task=, com.docker.swarm.task.id=sigof5ppeib20i443fjb4xirc, com.docker.swarm.task.name=container-manager.1.sigof5ppeib20i443fjb4xirc, databox.type=container-manager, image=databoxsystems/container-manager-amd64:0.5.0, name=container-manager.1.sigof5ppeib20i443fjb4xirc)
2018-10-03T14:31:44.259686321+01:00 network disconnect 687f694425a57d32592e1c98f76ac2239d55811d246fb5f47ea7276b1cc882a0 (container=69911ed152fe773a1f99fa890fae647c0fc17da1022909ad1dd99427ce71b5c3, name=bridge, type=bridge)
2018-10...
and when I look at the current containers:
dbnuc@dbnuc:~$ docker container ls -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
79e53ef5e3e6 databoxsystems/container-manager-amd64:0.5.0 "./app" 4 seconds ago Created container-manager.1.vz820cyl2y0ojbx83ot2pv9yl
fa686e0facac databoxsystems/container-manager-amd64:0.5.0 "./app" 9 seconds ago Created container-manager.1.rlekndcia9sgdvn9jx02akjx6
ec0aa311eede databoxsystems/container-manager-amd64:0.5.0 "./app" 14 seconds ago Created container-manager.1.1cgtt1jp1sddn3ey78wal3f8t
781d4dd1c8d9 databoxsystems/container-manager-amd64:0.5.0 "./app" 20 seconds ago Created container-manager.1.wlzohqrcr2ia52nauuuayv64c
63b760a7ef6a databoxsystems/container-manager-amd64:0.5.0 "./app" 25 seconds ago Created container-manager.1.kz6utlpnvsma72s90eptmn16w
e536a8a73ef7 databoxsystems/databox:latest "/databox start -v -…" 4 minutes ago Up 4 minutes confident_brown
dbnuc@dbnuc:~$ docker container ls -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
d0f2a3f50570 databoxsystems/container-manager-amd64:0.5.0 "./app" 2 seconds ago Created container-manager.1.a8fosr8sd9g19llgsm24r3hbt
79e53ef5e3e6 databoxsystems/container-manager-amd64:0.5.0 "./app" 8 seconds ago Created container-manager.1.vz820cyl2y0ojbx83ot2pv9yl
fa686e0facac databoxsystems/container-manager-amd64:0.5.0 "./app" 13 seconds ago Created container-manager.1.rlekndcia9sgdvn9jx02akjx6
ec0aa311eede databoxsystems/container-manager-amd64:0.5.0 "./app" 18 seconds ago Created container-manager.1.1cgtt1jp1sddn3ey78wal3f8t
781d4dd1c8d9 databoxsystems/container-manager-amd64:0.5.0 "./app" 24 seconds ago Created container-manager.1.wlzohqrcr2ia52nauuuayv64c
e536a8a73ef7 databoxsystems/databox:latest "/databox start -v -…" 4 minutes ago Up 4 minutes confident_brown
dbnuc@dbnuc:~$
I've run docker pull databoxsystems/databox:latest
but did not help.
what's the output of the following commands:
whoami
ls -la ./
hostname
pwd
docker version
I'm thinking the docker can't create the volumes for ./certs and ./sdk
Also when its crashing try running
docker service ps container-manager
are you using encrypted volumes/home folder or network mounts?
can you try the new release? Run:
docker run --rm -v /var/run/docker.sock:/var/run/docker.sock -v -t databoxsystems/databox:0.5.1 /databox start -sslHostName $(hostname)
The installation is okay now. Thanks.