Alliance in a container
See the alliance homepage
latest, latest-alpine, 0.3-alpine, 0.3.6-alpine: latest stable version on alpine linuxedge, edge-alpine, 1.0-alpine, 1.0.0-alpine: latest development version on alpine linux
Older versions can be used by requesting the specific tagged version i.e. 0.3.2-alpine
To start a basic default Alliance instance
docker run -name some-alliance -d codice/alliance
To expose the alliance ui:
docker run -name some-alliance -d -p 8993:8993 codice/alliance
To persist data/configurations mount either a volume container or a local folder to /app/data
To configure the system mount a volume container or local folder to /app/etc
To deploy bundles that are not packaged with the Alliance distribution mount a volume container or local folder to /app/deploy
Currently this container provides a custom entrypoint that has two hooks for pre-start and post start configuration.
To apply custom configuration steps before startup, mount a script via docker volumes to /opt/entrypoint/pre_start.sh
To apply custom configuration steps after startup, mount a script via docker volumes to /opt/entrypoint/post_start.sh
| Port | Purpose |
|---|---|
| 8101 | Alliance SSH server |
| 8181 | http |
| 8993 | https |
To build a specific image run make <version>/<os> where version corresponds to one of the version subdirectories and os corresponds to one of the base os images used (usually alpine or centos in this case). i.e. make 1.0.0/alpine
To build the latest and edge (and other floating tags) versions run make images. This will always build latest and edge as well as any other symlinked version. Symlinked folders are treated as floating tags for docker. Floating tags would be ones like latest (always the latest stable release), edge (latest development build), 1.0 (latest 1.0.x release)
This project utilizes manifest lists so that multi-arch image support can be added in the future. To push manifest list objects run make manifests.