This is a small collection of Dockerfiles I've been creating mostly for learning and testing purposes.
They can be used to build Docker images, usually by running docker build .from inside the Dockerfile's directory. You can also find almost all the images on my Docker Hub repository: https://hub.docker.com/u/gerardvivancos/.
You can pull the builds from Docker Hub with docker pull gerardvivancos/image-name or build an image from the Dockerfiles on this repo: docker build -t your-image-tag github.com/GerardVivancos/docker-containers/path/to/Dockerfile)
Intent is supposed to be clear from the directory name, so Dockerfile inside an nginx directory is expected to build an Nginx server. Some of them include specific instructions.
Please feel free to come back to me with improvements.
This will create an image enabled to run the latest Microsoft Azure CLI for Linux. Autocompletion is enabled.
This will create an image enabled to run the latest AWS CLI. It is useful because each container can use it's own AK/SK set, so with multiple containers you can manage multiple accounts with no conflicts. It also prevents you from potential Python version conflicts with your host system's installation.
It builds an image with Ruby 2.2.0 installed, compliled from source. It also installs Bundler.
It builds a minimal (~2MB) image based on busybox that creates a volume in /data. It's purpose is to serve as a shared volume across related containers.
Builds an image for local dynamodb development. By default, it uses data persistence to a volume mounted on /opt/dynamodb/data. You can override that behaviour and make it use the RAM with no persistence when creating your container: docker run -d -P --name your-meaningful-name your-image-tag "-inMemory"
Builds an image (~2MB) based on Busybox that starts the vi editor. Intended usage is to edit files on shared volumes. When you launch a container based on it, pass the path to the file to be opened. Example: docker run -ti --rm your-image-tag --volumes-from some-other-container /path/to/file (the --rm flag deletes the container after editing is done)
Builds an image (~2MB) based on Busybox that lists a directory (it just launches ls -l). Intended usage is to list directories on shared volumes. When you launch a container based on it, pass the path to the directory to be listed. Example: docker run -ti --rm your-image-tag --volumes-from some-other-container /path/to/directory (the --rm flag deletes the container after editing is done)
Builds an image to create containers running the BIND DNS server. Containers should be run with something like docker run -d -p 53:53/tcp -p 53:53/udp --your-meaningful-name your-image-tag
If you need to change the configuration once the container is running, just use the vi container (gerardvivancos/vi) or similar and attach it to the volume of the DNS server container: docker run -ti --rm --volumes-from dns-server-container-name gerardvivancos/vi /var/named/named.conf. You can also add new files -such as zone definitions- in the same way. When you're done editing, just restart the DNS container: docker restart dns-server-container-name.
Keep in mind that the default allow-query options won't let you query the DNS server from outside the Docker host. This is because the options localhost and localnets refer to the virtual network range of the container and queries made from the local network of the host are seen as being made from outside the network of the container. You might want to edit named.conf and add your local network CIDR to the allow-query directive (for example: allow-query { localhost; localnets; 192.168.0.0/16; };)
This builds a base image with Jekyll (http://jekyllrb.com). You can either pass commands to it when creating the container or use the specific tasks images
This builds an image based on gerardvivancos/jekyll, although you can change it to reference you own image name if you build one from the Dockerfile you can find inside the jekyll/jekyll folder on this repo (or have an equivalent one).
It is supposed to be used like this: docker run --rm -v /path/to/your/local/source/:/source -v /path/to/your/local/destination/:/destination your-image-tag, but you can be more creative and link it with other containers via volumes-from. In the end you should have your site built on path/to/your/local/destination
This builds an image based on gerardvivancos/jekyll, although you can change it to reference you own image name if you build one from the Dockerfile you can find inside the jekyll/jekyll folder on this repo (or have an equivalent one).
It is supposed to be used like this: docker run --rm -P -v /path/to/your/local/source/:/source -v /path/to/your/local/destination/:/destination gerardvivancos/jekyll-serve, but you can be more creative and link it with other containers via volumes-from. In the end you should have your site built on path/to/your/local/destination and be able to browse it by pointing to the Docker host IP on the exposed port.
A simple Nodejs installation. Entrypoint is /usr/bin/node, so you can pass parameters to NodeJS as parameters to the docker run command