“docker-compose up” fails with error

I want to work on a project, but I need to use docker for running the app, but the docker-compose up command fails with this error:

System error: exec: "./wait_to_start": stat ./wait_to_start:
no such file or directory

The wait_to_start command is an executable python script in the subfolder backend/.

  • Docker: Give container user write access to host directory
  • Docker Remote API returns 500 error on create container
  • How to connect to mysql using ipv6 from wordpress
  • How to use docker inside docker container in a save way
  • Installing Docker with script on Windows
  • How to scale out VMs in Azure Container Service Docker?
  • I need to determine why it cannot be executed. Either it’s been searched in the wrong path, or there are access right problems, or maybe the wrong python version is used.

    Can I debug it with details, or login with SSH and check the files on the virtual machine? I’m too unexperienced with Docker…

  • fio: blocksize too large for data set
  • How to pass parameters while creating consul client agent inside a Docker container?
  • Nancy on Linux is using 100% CPU
  • Docker-compose not passing environment variable to container
  • Is it proper to run a Docker image on a host with a different system?
  • Docker - Run Apache on host and container for different websites
  • 2 Solutions collect form web for ““docker-compose up” fails with error”

    You can either set the “workdir” metadata to make sure you are in the right place when you start a container or simply call /backend/wait_to_start instead of ./wait_to_start so you remove the need to be in the proper directory.

    Do debug with docker-compose I would do this:

    docker-compose run --entrypoint bash <servicename>

    That should give you a prompt and let you inspect the file and working directory, so see what’s wrong.

    Docker will be the best open platform for developers and sysadmins to build, ship, and run distributed applications.