diff options
author | 2020-05-15 00:46:30 -0700 | |
---|---|---|
committer | 2020-05-15 00:54:08 -0700 | |
commit | ceb8c226817080934e66edf2e158a881a104a0b3 (patch) | |
tree | 65038d8bf6a7dc0674037c7b5d2b9165c95bf697 /docker-compose.override.yml | |
parent | Propagate the git commit we built at into the env. (diff) | |
download | soko-ceb8c226817080934e66edf2e158a881a104a0b3.tar.gz soko-ceb8c226817080934e66edf2e158a881a104a0b3.tar.bz2 soko-ceb8c226817080934e66edf2e158a881a104a0b3.zip |
Add image: titles in the override.
When I run docker-compose up; it attempts to build the containers. This
is correct, but on my Ubuntu box for some silly reason go thinks my
kernel is bad and needs a higher ulimit set to memlock the signal stack
(a known golang bug.) I can do this in docker build (via --ulimit to
docker build) but docker-compose offers no such luxury when calling
docker build.
So by naming them in the docker-compose file, I can run docker build by
hand to produce the containers, and then docker compose just starts and
stops them.
Signed-off-by: Alec Warner <antarus@gentoo.org>
Diffstat (limited to 'docker-compose.override.yml')
-rw-r--r-- | docker-compose.override.yml | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/docker-compose.override.yml b/docker-compose.override.yml index b9210f5..20a0357 100644 --- a/docker-compose.override.yml +++ b/docker-compose.override.yml @@ -14,6 +14,7 @@ services: - 127.0.0.1:5000:5000 depends_on: - db + image: http-serving updater: build: context: . @@ -36,6 +37,7 @@ services: # SOKO_DEBUG: 'true' depends_on: - db + image: updater db: image: postgres:12 restart: always |