You want to have apps running in docker container. why?
#>cd ~/workspace
- Its convenient, to upgrade and twea k the app independent of changes to your own OS.
- To have multiple images of upgrade apps, which you know are experimental and buggy.
- Ship-able, so things can be shared in a way which is exactly reproduce-able
- Hype!
How to do it in the easiest of ways.
Git checkout - https://github.com/jfrazelle/dockerfiles
Someone has put a lot of hardwork and have made all the dockerfiles for most of the things you need -
It is an exhaustive list.
Build it, hack it, resubmit it, use it!
I use the firefox, chrome, tor, slack containers. The sound is a bit buggy and doesnt work straight out of the box. Here are some blogs to get you started - Jassie Frazelle's Container on desktop, Setting the sound up.
Here is how I build and fired up chrome -
#>cd ~/workspace
#>git clone https://github.com/jfrazelle/dockerfilescd
#>cd dockerfiles
#>docker build -t saneax/chrome-stable chrome/stable/
#>docker build -t saneax/chrome-stable chrome/stable/
#>docker run -it --rm \
--net host \
--cpuset-cpus 0 \
--memory 512mb \
-v /tmp/.X11-unix:/tmp/.X11-unix:rw \
-v /dev/snd:/dev/snd \
--privileged \
-v /dev/shm:/dev/shm \
-v /etc/machine-id:/etc/machine-id \
-v /var/lib/dbus:/var/lib/dbus \
-v /run/user/`id -u`/pulse/native:/run/user/`id -u`/pulse/native \
-v ~/.pulse:/home/$dockerUsername/.pulse \
--name chrome saneax/chrome
Happy docking!
No comments:
Post a Comment