Open cryptowally opened 4 years ago
I assume the values defined in the config.env file are intended for this purpose.
DOCKER_REPO=ecosi
APP_NAME=bastillion
VERSION=3.06.03
BASTILLION_FILENAME_VERSION=3.06_03
DOCKERIZE_VERSION=0.6.1
And read by the makefile:
# import config.
# You can change the default config with `make cnf="config_special.env" build`
cnf ?= config.env
include $(cnf)
Im unsure why this would not be working.
It seems someone has forked and cleaned up the docker file:
https://github.com/SteveCliff/docker-bastillion
He has hard coded the environment variables and removed the config file.
I tried to load this up with the Dockerfile that came with it, but it failed during the first wget.
I updated the ARG section of the dockerfile to this:
since those are the latest versions I could find, and then it built.
Is the Dockerfile, or parent host somehow supposed to supply these environment variables?
btw, I'm launching this via
docker-compose
instead ofdocker run
so I can bundle it with nginx more easily. Not sure if that's relevant or not.I cloned this repo into the directory and renamed it to "bastillion-docker"
docker-compose.yml:
The nginx proxy forwards 80-->8080 and 443->8443 but I don't have that part working yet. For now I just want bastillion running, and then I'll customize further for HTTPS, custom SSH keys, etc.