picoded/jenkins Docker 镜像 - 轩辕镜像 | Docker 镜像高效稳定拉取服务

Summary

This repository contains a collection of "Dockerfile" for their respective automated build in Docker hub, found at [***]

hub.docker.com

Note that if your seeing this README directly in docker, chances are you are using one of the images that will either be in the process of being rewritten. Or replaced;

Issue filling

Any problems / comments / kudos should be filed at github =) [***]

Overhaul in progress

Note that gradually overtime, I would be refactoring these various file to a more structured format

Organized Dockerfile

See their respective README for more details. These Dockerfile, typically represents various iterations, of all my DevOps docker experiences. Refined for multiple use cases.

(base)[[***]]

Base ubuntu images, with additional module (such as openjdk) installed. Used to build applications runners.

• (ubuntu-base)[[***]]
• (ubuntu-openjdk-8-jdk)[[***]]

git-cloner

Clones a git repository, and runs a command on it.

• (git-cloner-base : Ubuntu-base image, with git clone)[[***]]
• (git-cloner-plus : With additional preinstall module, like java, or npm)[[***]]
• git-cloner-* (see: git-cloner-plus)[[***]]

zip-cloner

Download a zip file, unzip it, and runs a command on it.

• (zip-cloner-base : Ubuntu-base image, with git clone)[[***]]
• (zip-cloner-plus : With additional preinstall module, like java, or npm)[[***]]
• zip-cloner-* (see: zip-cloner-plus)[[***]]

runner(s)

Start container, runs the respective action. Ends. Useful for onetime setup.

• (file-runner : Write content to a file)[[***]]
• (mysql-runner : Execute a mysql query)[[***]]
• (curl-post-runner : Runs a curl POST request)[[***]]

Unorganized Dockerfile

Every other folder not in organized Dockerfile, ranges from awesome, to crap, to not working.

Even I was a Docker noob once, and had to start from somewhere =P

License

MIT License

This is an obvious choice due to the highly public nature of these Docker repo's and how easy, or commonly the scripts can be replicated.

For most of the Dockerfiles, I wager that someone out there has something similar.

Hopefully mine is better, Cheers!

Best Regards, Eugene @ Picoded.com

Some general guidelines

• Follow the standard environment as specified inside (base/README)[[***]]
• Do not include external files (where practical), echo and write it out in Dockerfile instead.
  • This is because with layers and layers of file add, is un-viewable and un-traceable in Docker hub.
• Have a sane default for everything (if possible).
  • I want things to be deployable without configuration
  • Exception is for databases, or similar integration
• For application servers, build using (ubuntu-base)[[***]]
  • For everthing else priotise according to the following : Offical repo, alpine, busybox, debian, ubuntu-base