normes/docker-inbound-agent

Docker image for inbound Jenkins agents

https://badges.gitter.im/jenkinsci/docker.svg](https://gitter.im/jenkinsci/docker?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge) https://img.shields.io/github/stars/jenkinsci/docker-inbound-agent?label=GitHub%20stars](https://github.com/jenkinsci/docker-inbound-agent) https://img.shields.io/docker/pulls/jenkins/inbound-agent.svg](https://hub.docker.com/r/jenkins/inbound-agent/) https://img.shields.io/github/release/jenkinsci/docker-inbound-agent.svg?label=changelog](https://github.com/jenkinsci/docker-inbound-agent/releases/latest)

:exclamation: Warning! This image used to be published as https://hub.docker.com/r/jenkinsci/jnlp-slave/ and https://hub.docker.com/r/jenkins/jnlp-slave/. These images are deprecated, use https://hub.docker.com/r/jenkins/inbound-agent/.

This is an image for https://jenkins.io agents using TCP or WebSockets to establish inbound connection to the Jenkins master. This agent is powered by the https://github.com/jenkinsci/remoting, which version is being taken from the base https://github.com/jenkinsci/docker-agent/ image.

See https://wiki.jenkins-ci.org/display/JENKINS/Distributed+builds for more info.

Running

To run a Docker container

Linux agent:

docker run --init jenkins/inbound-agent -url [***] <secret> <agent name>

Note: --init is necessary for correct subprocesses handling (zombie reaping)

Windows agent:

docker run jenkins/inbound-agent:windowsservercore-1809 -Url [***] -Secret <secret> -Name <agent name>

To run a Docker container with https://github.com/jenkinsci/remoting/blob/master/docs/workDir.md

Linux agent:

docker run --init jenkins/inbound-agent -url [***] -workDir=/home/jenkins/agent <secret> <agent name>

Windows agent:

docker run jenkins/inbound-agent:windowsservercore-1809 -Url [***] -WorkDir=C:/Jenkins/agent -Secret <secret> -Name <agent name>

Optional environment variables:

• JENKINS_URL: url for the Jenkins server, can be used as a replacement to -url option, or to set alternate jenkins URL
• JENKINS_TUNNEL: (HOST:PORT) connect to this agent host and port instead of Jenkins server, assuming this one do route TCP traffic to Jenkins master. Useful when when Jenkins runs behind a load ***, reverse proxy, etc.
• JENKINS_SECRET: agent secret, if not set as an argument
• JENKINS_AGENT_NAME: agent name, if not set as an argument
• JENKINS_AGENT_WORKDIR: agent work directory, if not set by optional parameter -workDir
• JENKINS_WEB_SOCKET: true if the connection should be made via WebSocket rather than TCP

Configuration specifics

Enabled JNLP protocols

As of version 3.40-1 this image only supports the https://github.com/jenkinsci/remoting/blob/master/docs/protocols.md#jnlp4-connect protocol. Earlier, long-unsupported protocols have been removed. As a result, Jenkins versions prior to 2.32 are no longer supported.

Amazon ECS

Make sure your ECS container agent is http://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-agent-update.html before running. Older versions do not properly handle the entryPoint parameter. See the http://docs.aws.amazon.com/AmazonECS/latest/developerguide/task_definition_parameters.html#container_definitions definition for more information.