https://github.com/cha87de/docker-skeleton

Docker skeleton with best practice for writing dockerfile & entrypoint - bash only. Reliable Docker containers with fail fast and retry logic.
https://github.com/cha87de/docker-skeleton

cloud-native docker entrypoint skeleton

Last synced: 10 months ago
JSON representation

Docker skeleton with best practice for writing dockerfile & entrypoint - bash only. Reliable Docker containers with fail fast and retry logic.

• Host: GitHub
• URL: https://github.com/cha87de/docker-skeleton
• Owner: cha87de
• License: gpl-3.0
• Created: 2018-03-02T19:40:21.000Z (over 8 years ago)
• Default Branch: master
• Last Pushed: 2019-02-11T09:10:58.000Z (over 7 years ago)
• Last Synced: 2025-04-14T23:42:00.656Z (about 1 year ago)
• Topics: cloud-native, docker, entrypoint, skeleton
• Language: Shell
• Homepage:
• Size: 37.1 KB
• Stars: 10
• Watchers: 1
• Forks: 2
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

          
# docker-skeleton

A docker skeleton - with best practice guide for writing dockerfile & entrypoint.

Assumptions:

 - simple bash based entrypoint

 - one to many services to be configured and started

 - file based configuration files, modified by environment variables

 - reliable, immutable bootstrapping

 - fail fast & retry in entrypoint and for whole container

Keep it simple. Bash solves all your needs. No complex service or daemon for bootstrapping needed.

The entrypoint as a flow chart diagram:

![](flowchart.png)

## Experiences

With the presented approach, we managed to build a real OpenStack test setup - with approx. 30 physical nodes and hence approx. 300 containers in total: [Omistack](https://omistack.anyops.org).

# TODOs and Extensions

 - [ ] add side kick container skeleton to host (configuration) data

 - [ ] extract execution steps out of entrypoint and allow their definition in simple yaml file