Dockerized java developer environment.
252
Basically a dockerized java developer environment. I've been successfully using this for almost one year now and have no regrets whatsoever. It includes out-of-the-box the most used packages by java developers. The main dev tool in this version is Eclipse Oxygen. Full stack description can be found bellow:
unzip locales tree vim htop git subversion build-essential sudo ssh libgtk-3-0 libxtst-devdeveloper (gip:uid = 1000:1000) is the default user. It has sudo (without password) powers./opt//usr/bin folder to the main programs as follows:
mvnjavaeclipse-jeeeclipse-rcp/bin/bash by default.run.sh with the parameters necessary to open graphic applications in docker../run --name my_container fabiofranco/java-developerdocker attach my_container. Do your cli stuff!docker exec -it my_container eclipse-jee. After eclipse starts you can detach from the docker terminal by pressing Ctrl+P and Ctrl+Q (dont release the Ctrl key between the P and Q)In my experience it is a very effective practice to map a persistent docker volume into an isolated folder that I usually call isolation in $HOME directory.
This will centralize all the data you need persisted and allow you to consider your container disposable.
Even files or folder you need to be in the home folder AND persisted can be placed there by links. For instance, if I want my maven repository to be persisted (and/or shared) beteween containers I create a maven repository folder into this isolated volume and create a symlink in the home folder as shown in the example bellow.
[my_host_user@localhost ~]$ docker volume create test
test
[my_host_user@localhost ~]$ ./run.sh --name my_container -v test:/home/developer/isolation fabiofranco/developer
developer@xxxxxxxxxxxx:~$ sudo chown -R 1000:1000 isolation
developer@xxxxxxxxxxxx:~$ mkdir -p isolation/_env/mvn
developer@xxxxxxxxxxxx:~$ ln -s isolation/_env/mvn .m2
Content type
Image
Digest
Size
2.8 GB
Last updated
over 8 years ago
docker pull fabiofranco/developer