Skip to content

nettworks-e-V/fli4l-3.10-buildroot-buildnode

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

12 Commits
 
 
 
 
 
 
 
 

Repository files navigation

Docker container with fli4l Buildroot

This is a docker implementation of fli4l buildroot buildnode for Jenkins.

For more information please refer to Official website or Support forum

1. Install docker

This instruction works for a Centos7 docker host. Other distributions may need some adjustments.

sudo tee /etc/yum.repos.d/docker.repo <<-'EOF'
[dockerrepo]
name=Docker Repository
baseurl=https://yum.dockerproject.org/repo/main/centos/7/
enabled=1
gpgcheck=1
gpgkey=https://yum.dockerproject.org/gpg
EOF
...
sudo yum install docker-engine -y
...
sudo systemctl enable docker.service
...
sudo systemctl start docker.service

2. Build/Use the Container

You now have two options:

  • Build from scratch or
  • Pull the ready-made image from DockerHub.

2a Image from Docker Hub

sudo docker pull starwarsfan/fli4l-buildroot-buildnode

2b Build from scratch

Pull repo from github
sudo git clone https://github.com/starwarsfan/fli4l-buildroot-buildnode.git
cd fli4l-buildroot-buildnode
Build image
sudo docker build -t starwarsfan/fli4l-buildroot-buildnode:latest .

3. Starting docker container

sudo docker run \
    --name fli4l-buildroot-buildnode** \
    -d \
    starwarsfan/fli4l-buildroot-buildnode:latest

3.a Mountpoints

There are the following mountpoints available:

  • /data/work/
  • /data/shared/fli4l/
  • /home/jenkins/.ssh/

These mountpoints can be used to mount folders from the host or other volumes to store informations which should be persistant or should not everytime be recreated.

With the additional run parameter -v :/data/work/ you can mount a folder on the docker host which contains persistant data. So the run command may look like the following example:

sudo docker run \
    --name fli4l-buildroot-buildnode \
    -v /data/svn-checkout/:/data/work/ ...

3.b Available options

The container could be startet with some of the following options. These list contains the default values, which could be overwritten on the docker run command:

  • JENKINS_URL=http://localhost
  • JENKINS_TUNNEL=
  • JENKINS_USERNAME=admin
  • JENKINS_PASSWORD=admin
  • EXECUTORS=1
  • DESCRIPTION=Swarm node with fli4l buildroot
  • LABELS=linux swarm fli4l-buildroot
  • NAME=generic-swarm-node
sudo docker run \
    --name fli4l-buildroot-buildnode \
    -e "JENKINS_URL=https://jenkins.foobar.org" \
    -e "JENKINS_PASSWORD=123456" ...

3.c Jenkins behind reverse proxy

The option JENKINS_TUNNEL might be neccessary if Jenkins is running behind a reverse proxy as the JNLP connection could not be established in such a setup. You need to configure the following on Jenkins:

  • Configuration > Global Security > Agents
  • Set TCP port for JNLP agents to Static
  • Enter a port number like 32775
  • Save configuration

Assumed your Jenkins is available on https://jenkins.foobar.org, the host has the ip 10.20.30.40 and you configured the JNLP port 32775, you need to start the container with at least these options:

sudo docker run \
    --name fli4l-buildroot-buildnode \
    -e "JENKINS_URL=https://jenkins.foobar.org" \
    -e "JENKINS_TUNNEL=10.20.30.40:32775" ...

4. Useful commands

Check running / stopped container:

sudo docker ps -a

Stop the container

sudo docker stop fli4l-buildroot-buildnode

Start the container

sudo docker start fli4l-buildroot-buildnode

Get logs from container

sudo docker logs -f fli4l-buildroot-buildnode

Open cmdline inside of container

sudo docker exec -i -t fli4l-buildroot-buildnode /bin/bash

Releases

No releases published

Packages

No packages published

Contributors 3

  •  
  •  
  •