Use docker-compose to manage the containers, and start ceod automatically. The service can be restarted with SIGHUP sent by docker/docker-compose.
Hm, I don't know...I personally prefer my shell script since it only has two commands (up and down),
and it's easy to stop a process (with Ctrl-C).
Maybe we can include both?
nc -l 0.0.0.0 9002 &
This is necessary for Drone, since service containers exit after the last command.
If you don't want this in the shell script, then you need to add it back into .drone.yml.
ldapadd -c -f .drone/data.ldif -Y EXTERNAL -H ldapi:///
if [ -z "$CI" ]; then
ldapadd -c -f .drone/uwldap_data.ldif -Y EXTERNAL -H ldapi:///
ldapadd -c -f .drone/uwldap_data.ldif -Y EXTERNAL -H ldapi:/// ||:
Why are we ignoring the error? Are you trying to make the script idempotent?
Yeah. This is actually not the optimal setup with Docker with these setup scripts running every time it starts. But this is the minimal change for a running Docker setup without recreating and rerunning everything everytime.
# sync with phosphoric-acid
nc -l 0.0.0.0 9000
Same comment as above.
docker-compose exec phosphoric-acid bash
su ctdalek # optional, to run as normal user
kinit ctdalek # password is krb5
Logging in as ctdalek will automatically acquire a Kerberos ticket (via libpam-krb5).
Ah, good to know.
if [ "$host" = auth1 ]; then
exec sleep infinity
python3 -m pip install -r requirements.txt -r dev-requirements.txt
The venv should be installed on the host - this will save a lot of disk space.
docker run --rm -v "$PWD:$PWD" -w "$PWD" python:3.7-buster \
sh -c "python -m venv venv && . venv/bin/activate && pip install -r dev-requirements.txt && pip install -r requirements.txt"
docker network create ceod
I don't see this anywhere in your docker-compose.yml? (the docker network)
docker-compose automatically creates a network using the project name for all services defined in the file, so we don't need to create one manually.
You can start docker-compose in the foreground (and have Ctrl-C working) by not using the -d flag.
No due date set.
No dependencies set.
Deleting a branch is permanent. It CANNOT be undone. Continue?