|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|