Public | Automated Build

Last pushed: 2 years ago
Short Description
This is the Vynosny web application container
Full Description

Run Command

docker run  --log-driver=none -v /srv/vynosny:/data -d -p 443:8443 --volumes-from jenkins --name vynosny --restart=always rerosum/vynosny


  • The service file is 'inoticoming_watched' and goes in: /etc/init.d/
    sudo chmod u+x /etc/init.d/inoticoming_watched
    sudo update-rc.d inoticoming_watched defaults
    cat /srv/vynosny/trigger.log
  • The restart script file '' goes in /srv/vynosny
    sudo chmod u+x /srv/vynosny/


Download package

wget -O splunk-6.2.5-272645-linux-2.6-amd64.deb ''
dpkg -i splunk-6.2.5-272645-linux-2.6-amd64.deb
sudo /opt/splunk/bin/splunk enable boot-start
sudo /opt/splunk/bin/splunk start --accept-license
  • Copy splunk.conf to /etc/init
  • User name = 'admin', password = '052569'


  • [Cheat sheet] (

  • Build a new image from local Dockerfile (best to build on docker hub for vynosny image)

      sudo docker build --no-cache --rm -t rerosum/jenkins .
      sudo docker build --no-cache --rm -t rerosum/vynosny .
  • Tag the image with a name

      sudo docker tag {image id} rerosum/jenkins
  • Push a new image up to docker hub

      sudo docker push rerosum/jenkins
      sudo docker push rerosum/vynosny
  • Pull latest images from docker hub for vynosny & jenkins

      docker pull rerosum/vynosny
      docker pull rerosum/jenkins
  • List containers

      sudo docker ps
  • Get bash shell into a container

      docker exec -it jenkins /bin/bash
  • Run docker container as daemon process with a restart policy

      docker run -v /srv/vynosny/data:/data -d -p 443:8443 --volumes-from jenkins --name vynosny --restart=always rerosum/vynosny
      docker run -v /srv/jenkins:/var/lib/jenkins -d --name jenkins -p 9080:8080 --restart=always rerosum/jenkins
  • Update image after modifying container

      docker commit -m "Updated with Jenkins config" {container id} rerosum/jenkins:v2
  • View logs for a container

      sudo docker logs vynosny
  • Top command

      ID=$(sudo docker run -d rerosum/vynosny /usr/bin/top -b)
      sudo docker attach $ID
  • Notes

    • Removing a container ALSO removes it's persisted VOLUMEs. This is corrected by mounting a host directory as a
      volume in the container (see above run commands)
    • Process to copy data out of a conatiner to host, then back into a container
    • Copy a VOLUME from container to host
      docker cp jenkins:/var/lib/jenkins /var/tmp
      docker cp vynosny:/data /var/tmp
    • Mount host dir in new container
      docker run -v /var/tmp:/host -d --name jenkins -p 9080:8080 --restart=always rerosum/jenkins
      docker run -v /var/tmp:/host -d --name vynosny --volumes-from jenkins -p 443:8443 --restart=always rerosum/vynosny
    • Copy files from mounted host directory back into container (log into container with bash shell)
      cp -a /host/jenkins /var/lib
      cp -a /host/data /
Docker Pull Command
Source Repository