How to set up the Docker API?

Question

linux

I'm trying to integrate Jenkins and Docker, but something is going wrong. Docker runs on Centos 7.
I set up the docker according to the instructions, launched it on port 4243. There are also two Jenkins. One is raised in a docker container, the second is raised on another server. The purpose nevertheless to configure on the second jenkins.
The first one when testing docker access returns: Version = 1.11.2-rc1.
Second - Something went wrong, cannot connect to xxxx:4243 , cause: null
Docker Plugin installed on jenkins ( from here )
Docker version: Docker version 1.11.2-rc1, build
1179573
as such, there are no errors.
But for some reason, every 3-5 minutes the text of the following plan:

Jun 02 05:25:01 name.server kernel: SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs
Jun 02 05:25:01 name.server systemd[1]: Created slice user-991.slice.
-- Subject: Unit user-991.slice has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit user-991.slice has finished starting up.
-- 
-- The start-up result is done.
Jun 02 05:25:01 name.server systemd[1]: Starting user-991.slice.
-- Subject: Unit user-991.slice has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit user-991.slice has begun starting up.
Jun 02 05:25:01 name.server systemd[1]: Started Session 7751 of user pcp.
-- Subject: Unit session-7751.scope has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit session-7751.scope has finished starting up.
-- 
-- The start-up result is done.
Jun 02 05:25:01 name.server systemd[1]: Starting Session 7751 of user pcp.
-- Subject: Unit session-7751.scope has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit session-7751.scope has begun starting up.
Jun 02 05:25:01 name.server CROND[2551]: (pcp) CMD ( /usr/libexec/pcp/bin/pmlogger_check -C)
Jun 02 05:25:02 name.server systemd[1]: Removed slice user-991.slice.
-- Subject: Unit user-991.slice has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit user-991.slice has finished shutting down.
Jun 02 05:25:02 name.server systemd[1]: Stopping user-991.slice.
-- Subject: Unit user-991.slice has begun shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit user-991.slice has begun shutting down.

Commands were also executed:
systemctl disable firewalld
systemctl stop firewalld
Below are files with docker settings:
/usr/lib/systemd/system/docker.service

[Unit]
Description=Docker Application Container Engine
Documentation=https://docs.docker.com
After=network.target docker.socket
Requires=docker.socket

[Service]
Type=notify
# the default is not to use systemd for cgroups because the delegate issues still
# exists and systemd currently does not support the cgroup feature set required
# for containers run by docker
EnvironmentFile=-/etc/sysconfig/docker
ExecStart=/usr/bin/docker daemon -H fd:// $DOCKER_OPTS
MountFlags=slave
LimitNOFILE=1048576
LimitNPROC=1048576
LimitCORE=infinity
TimeoutStartSec=0
# set delegate yes so that systemd does not reset the cgroups of docker containers
Delegate=yes

[Install]
WantedBy=multi-user.target

/etc/sysconfig/docker

DOCKER_OPTS="-H tcp://0.0.0.0:4243 -H unix:////run/docker.sock"

What, where else can you see how to set up Docker?

Answer 1

yes, the problem was solved by installing a newer version of jenkins. Was 1.5.