Docker exit code 137 may imply Docker doesn’t have enough RAM to finish the work.
Unfortunately Docker consumes a lot of RAM.
Go to Docker Desktop app > Preferences > Resources > Advanced
and increase the MEMORY – best to double it.
More Related Contents:
- Docker Compose wait for container X before starting Y
- Communication between multiple docker-compose projects
- Using Docker-Compose, how to execute multiple commands
- What is the difference between docker-compose ports vs expose
- How to mount a single file in a volume
- Docker: How to clear the logs properly for a Docker container?
- Docker : Can a container A call an executable located on an other container B?
- How to specify Memory & CPU limit in docker compose version 3
- How to pass arguments within docker-compose?
- How do I mount a host directory as a volume in docker compose
- Re-using environment variables in docker-compose.yml
- How to use the host network, and any other user-defined network together in Docker-Compose?
- What is the difference between ports and expose in docker-compose?
- How to use environment variables in docker-compose?
- Why the “none” image appears in Docker and how can we avoid it
- How do I set hostname in docker-compose?
- How to mount local volumes in docker machine
- Is it safe to clean docker/overlay2/
- Connect to Kafka on host from Docker (ksqlDB)
- Using docker-compose with CI – how to deal with exit codes and daemonized linked containers?
- Kafka access inside and outside docker [duplicate]
- How do I configure docker compose to expose ports correctly?
- Where is a log file with logs from a container?
- docker-compose build environment variable
- How to pass arguments to a Dockerfile?
- How to tag docker image with docker-compose
- Pass argument to docker compose
- Docker 1.10 access a container by its hostname from a host machine
- Difference between “docker compose” and “docker-compose”
- how to get docker-compose to use the latest image from repository