Failed to Create Container - 500

ShinyProxy
#1

I’m almost loving shinyproxy… except I’ve got a failure with the current version of Docker.

I can run the docker samples from the command line, but there is a config file error when used with the new updated version of docker (on Centos 7 downloaded by yum) when run automatically.

docker version
Client:
Version: 1.13.1
API version: 1.26
Package version: docker-1.13.1-63.git94f4240.el7.centos.x86_64
Go version: go1.9.4
Git commit: 94f4240/1.13.1
Built: Fri May 18 15:44:33 2018
OS/Arch: linux/amd64

Server:
Version: 1.13.1
API version: 1.26 (minimum version 1.12)
Package version: docker-1.13.1-63.git94f4240.el7.centos.x86_64
Go version: go1.9.4
Git commit: 94f4240/1.13.1
Built: Fri May 18 15:44:33 2018
OS/Arch: linux/amd64
Experimental: false

The docker config files looks like:

Type=notify
NotifyAccess=all
EnvironmentFile=-/run/containers/registries.conf
EnvironmentFile=-/etc/sysconfig/docker
EnvironmentFile=-/etc/sysconfig/docker-storage
EnvironmentFile=-/etc/sysconfig/docker-network
Environment=GOTRACEBACK=crash
Environment=DOCKER_HTTP_HOST_COMPAT=1
#Environment=-H tcp://127.0.0.1:2375 -H unix://
Environment=PATH=/usr/libexec/docker:/usr/bin:/usr/sbin
ExecStart=/usr/bin/dockerd-current
–add-runtime docker-runc=/usr/libexec/docker/docker-runc-current
–default-runtime=docker-runc
–exec-opt native.cgroupdriver=systemd
–userland-proxy-path=/usr/libexec/docker/docker-proxy-current
–init-path=/usr/libexec/docker/docker-init-current
–seccomp-profile=/etc/docker/seccomp.json
$OPTIONS
$DOCKER_STORAGE_OPTIONS
$DOCKER_NETWORK_OPTIONS
$ADD_REGISTRY
$BLOCK_REGISTRY
$INSECURE_REGISTRY
$REGISTRIES
ExecReload=/bin/kill -s HUP $MAINPID
LimitNOFILE=1048576
LimitNPROC=1048576
LimitCORE=infinity
TimeoutStartSec=0
Restart=on-abnormal

#2

I forgot to mention, i’m running shinyproxy 1.1.1.

Erick

#3

It might be the firewall.

Or, what is the port 20000, why is it setable, and why 20000. Could I be looking at the wrong port?

Erick

#4

I see the java error:
Caused by: com.spotify.docker.client.exceptions.DockerException: java.util.concurrent.ExecutionException: javax.ws.rs.ProcessingException: org.apache.http.conn.HttpHostConnectException: Connect to localhost:2375 [localhost/127.0.0.1, localhost/0:0:0:0:0:0:0:1] failed: Connection refused (Connection refused

That matches up with my seeing the port listening on the command line when I run it manually, but being unable to open the port with telnet localhost 2375

Erick

#5

Hello Erick,

You need to configure docker to allow shinyproxy to interact with it as described in https://www.shinyproxy.io/getting-started/#docker-startup-options
In particular for CentOS 7 you need to modify ExecStart to be something like ExecStart=/usr/bin/dockerd -H fd:// -D -H tcp://127.0.0.1:2375

The port 20000 is the starting port for the containers, it can be modified, as described in https://www.shinyproxy.io/configuration/#docker (see port-range-start)

#6

But using that line alone gives:

Jul 06 08:13:59 dark2.uwaterloo.ca systemd[1]: Starting Docker Application Container Engine…
Jul 06 08:13:59 dark2.uwaterloo.ca dockerd-current[15255]: no sockets found via socket activation: make sure the service was started by systemd
Jul 06 08:13:59 dark2.uwaterloo.ca systemd[1]: docker.service: main process exited, code=exited, status=1/FAILURE
Jul 06 08:13:59 dark2.uwaterloo.ca systemd[1]: Failed to start Docker Application Container Engine.
Jul 06 08:13:59 dark2.uwaterloo.ca systemd[1]: Unit docker.service entered failed state.
Jul 06 08:13:59 dark2.uwaterloo.ca systemd[1]: docker.service failed.

Erick

#7

I’ve tried it with those options alone, failed with the error above.

I’ve tried it with those options merged with the default options from installation package. Failed with same error.

It appears anytime I use -H fd:// anywhere in the sequence, the daemon cannot start.

Erick

1 Like