Skip to content
master
Switch branches/tags
Go to file
Code

Latest commit

 

Git stats

Files

Permalink
Failed to load latest commit information.
Type
Name
Latest commit message
Commit time
bin
 
 
 
 
doc
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

README.md

Docker Project Template

Purpose

To provide the common files for building, running a docker project

Concepts

> Simple command-based Docker environments:

  • Open Source code for all containers: For community to extend or improve upon.
  • Hiding the details with one command to run or build: As simple as just one command to start a Docker-based applications without fudging and mistakes in launching containers.

> Container-based Development and Big Data Analytic Environments

  • Providing many commonly used "pure docker-based IDEs, Applications, Servers" for software development daily needs.
  • Supporting development (e.g. JDK, Python, ...) and advanced applications/servers (e.g., scala-ide-docker, Netbean-docker, Jupyter, Zeppelin, SparkNotebook, Eclipse-docker, and many other big data analytic, deep learning, machine learning, and semantic knowledge graph applications/servers).

> Only needs two scripts: "./run.sh" and "./build.sh"

  • "./run.sh" to instantly stand up and "./build/sh" to build containers.
  • For Product usage, please ensure all aspects of security by enhancing source code and setup.

> Build-time and Run-time Environment Variable files ".env" and "env_file.txt"

  • ".env" (for docker-compose exclusively only) or "docker.env" (our extension): "docker-compose" only environment variables. "docke-compose" command will automatically search for the file ".env" in the current directory.
  • : Build-time environment variables to overwrite those variables defined inside Dockefile If you have a file named .env in your project, it’s only used to put values into the docker-compose.yml file which is in the same folder. Those are used with Docker Compose and Docker Stack.
  • "docker-run.env" (our naming to use by run.sh): Docker run-time environment variables for "docker run ...". The script "run.sh" will search for this file to input as "--env-file=./docker-run.env" for "docker run ..." command.
  • e.g.
docker run --env-file=./docker-run.env ...

How to Google-Chrome running:

To start google-chrome, use the full command below

google-chrome --no-sandbox --disable-gpu --disable-extensions

Resources

  • This project template folder assumes you like to adopt and use simple command-based Docker life-cycle paradigm using containers:
  1. OpenKBS Docker HUB [https://hub.docker.com/r/openkbs/] - for pulling the ready to use public Docker Images.
  2. OpenKBS GIT HUB [https://github.com/DrSnowbird/] - for advanced users like to build and customize to your own flavor using our open source environments.

How to Use this template?

  1. Git clone or Copy all the folder's files to your destination, i.e., your new project folder.
  2. Globally replace "docker-project-template" for all the files with your new Docker project repo name, e.g., scala-ide-docker.
  3. Modify files below depending upon your use case: Dockerfile, docker-compose.yaml, or docker.env (if you need to modify docker environments input file)
  4. You don't have to modify the generic scripts, "build.sh" and "run.sh".
  5. (optional) Modify "build.sh" and "run.sh" if needed to change any of these two scripts - expert only!
  6. Add any Volumes you want auto mapping between Host and Docker Container: add volume entries in "docker.env" files - the file has explanation text in it. For example, to create two mapping of volumes, "data" and "workspace",
##- Rider configuration for run.sh ####
##- Use "#VOLUMES" and "#PORTS" to indicate that the variables for run.sh"
##-To ignore line, use "##" (double) in the beginning, 
##-  e.g. "##VOLUMES" and "##PORTS"
##-  - To indicate that the variables for run.sh", use only one "#",  
##-     e.g. "#VOLUMES" and "#PORTS"
#VOLUMES_LIST="data workspace"

Then, you are ready to build and run (see below).

Build

  • This project provides a simple Dockerfile for the purpose of illustration only. You need to extend/modify the Docker to support whatever you want to do.
./build.sh

(NEW) Configuration

New extension to allow users to enter "Volume mapping" and "Port mapping" entries together with "docker.env" file with "#" syntax to avoid docker-compose pick up the entries -- "Rider" configuration! Here is the example syntax:

## Rider configuration for run.sh ####
# - Use "#VOLUMES" and "#PORTS" to indicate that the variables for run.sh"
# - To ignore line, use "##" (double) in the beginning, e.g. "##VOLUMES" and "##PORTS"
# - To indicate that the variables for run.sh", use only one "#",  e.g. "#VOLUMES" and "#PORTS"
#VOLUMES_LIST="data workspace"
##PORTS_LIST="18080:8000 17200:7200"

Run

  • To run the simple example build image; it will pop up X11 to display Firefox docker-based browser. Note that the script "run.sh" is designed to generic for every project with assumption that it use the "current git directory name" to figure out the image name you may want to use.
./run.sh

Or,

docker-compose up

Or,

make up

Utility Scripts

Scripts under ./bin have several useful bash scripts to jump start what you need.

  1. dockerCE-install.sh: Install docker CE with latest version available.
  2. portainer_resume.sh: Launch portainer to manage all you desktop Docker containers.
  3. container-launcher.sh: Launch specific container using "pattern expression".

Corporate Proxy Root and Intemediate Certificates setup for System and Web Browsers (FireFox, Chrome, etc)

  1. Save your corporate's Certificates in the currnet GIT directory, ./certificates
  2. During Docker run command,
   -v `pwd`/certificates:/certificates ... (the rest parameters)

If you want to map to different directory for certificates, e.g., /home/developer/certificates, then

   -v `pwd`/certificates:/home/developer/certificates -e SOURCE_CERTIFICATES_DIR=/home/developer/certificates ... (the rest parameters)
  1. And, inside the Docker startup script to invoke the ~/scripts/setup_system_certificates.sh. Note that the script assumes the certficates are in /certificates directory.
  2. The script ~/scripts/setup_system_certificates.sh will automatic copy to target directory and setup certificates for both System commands (wget, curl, etc) to use and Web Browsers'.

References & Resources

Docker Finer-grained Access Control

Docker is a software that allows to run applications inside of isolated containers. Docker can associate a seccomp profile with the container using the --security-opt parameter. Using OPA, you can easily have finer-grained access control.

Setup Dockerfile Build behind Corporate Proxies

Proxy & Certificate Setup

For corporate with proxies, to build the images, you need to setup proxy. The better way to setup proxy for docker build and daemon is to use configuration file and there is no need to change the Dockerfile to contain your proxies setup.

With new feature in docker option --config, you needn't set Proxy in Dockerfile any more.

--config string : Location of client config files (default ~/.docker/config.json) or environment variable DOCKER_CONFIG

DOCKER_CONFIG : The location of your client configuration files.

(the following is default docker config file)
export DOCKER_CONFIG=~/.docker/config.json

It is recommended to set proxy with httpProxy, httpsProxy and ftpProxy in ~/.docker/config.json unless it is not feasible to set up this config file, e.g., in Openshift, or Kubernetes environments. You need to adjust the DNS proxy hostname according to your specifics of your corporate proxy.

{
    "proxies":
    {
        "default":
        {
            "httpProxy": "http://proxy.openkbs.org:80",
            "httpsProxy": "http://proxy.openkbs.org:80",
            "ftpProxy": "http://proxy.openkbs.org:80",
            "noProxy": "127.0.0.1,localhost,.openkbs.org"
        }
    }
}

Adjust proxy IP and port if needed and save to ~/.docker/config.json

About

Docker project template to quickly create a fully functional docker container

Topics

Resources

License

Packages

No packages published