Docker image for development.
Inherit from arnaudh/ubuntu-dev-base image
Install all the needed packages to have a working development environment inside a docker container:
- Google Chrome browse
- Mozilla Firefox
- Java 8u102
- That's it, but other applications will follow :)
The image will be tagged on the Docker Store for each new application, so it will be easy to inherit from this tag and build your own image.
Having the sound to work can be painful, as you have different configurations on your host. The aim it to use resources of the host (with volumes) to stream audio on the soundcard. This image uses the pulseaudio server of the host to play sounds.
It has been sucessfully tested with Ubuntu 16.04 host.
Run this image with the command :
USER_NAME=arnaudhb
USER_ID=`id -u`
IMG_NAME=$(basename $(pwd))
IMG_TAG=browser
docker run -it --rm \
-e DISPLAY=$DISPLAY \
-e PULSE_SERVER=/run/pulse/native \
-e PULSE_COOKIE=/run/pulse/cookie \
-v /tmp/.X11-unix:/tmp/.X11-unix \
-v /var/run/user/$USER_ID/pulse:/run/pulse \
-v /var/run/dbus:/var/run/dbus \
-v ~/.config/pulse/cookie:/run/pulse/cookie \
-v /etc/machine-id:/etc/machine-id \
-v /var/lib/dbus:/var/lib/dbus \
-v /dev/shm:/dev/shm \
-v /dev/dri:/dev/dri \
--security-opt seccomp:$PWD/chrome.json \
--group-add audio \
--group-add video \
$DOCKER_VOLUMES \
$USER_NAME/$IMG_NAME:$TAG
Inside the container, start Chrome with the command
$> chromeFeel free the use volumes to map user data dir (default in /root/.config/google-chrome) to be able to persist data over container starting.
Inside the container, start Firefox with the command
$> firefoxFeel free the use volumes to map user profiles dir (default in /root/.firefox) to be able to persist data over container starting.
Inside the container, check Java installation with the command
$> java -version
java version "1.8.0_102"
Java(TM) SE Runtime Environment (build 1.8.0_102-b14)
Java HotSpot(TM) 64-Bit Server VM (build 25.102-b14, mixed mode)If you start containers with a specific user, ensure root user is allowed to connect to the X11 server of the host :
xhost + si:localuser:rootAnd test with:
xeyesA sample WAV file is available for testing sound:
paplay /root/send.wavIt seems using sounds in the container (few developers can work without music :) ) breaks the pulseaudio server and disable the sound on the host. I didn't figure out why, but it can easily workarounded by killing pulseaudio server and let start-stop-daemon restart it automatically. Check the run.sh script to see a working example.
Anyway, you could listen music direcly from the host but having all enclosed within a container, without dependencies with the host (other than its resources), is a challenge :D
https://stackoverflow.com/questions/16296753/can-you-run-gui-apps-in-a-docker-container
http://stackoverflow.com/questions/28985714/run-apps-using-audio-in-a-docker-container
https://github.com/sameersbn/docker-browser-box
https://github.com/jessfraz/dockerfiles/tree/master/chrome/stable