docker: pelias_api stopped running, exit code 126
Describe the bug pelias/api:master container stopped running, will not restart, throws exit code 126. No configuration changes or updates were made recently before this issue started. I deleted the contents of the data folder and redownloaded everything.
Steps to Reproduce Run the Pelias start-up script:
mkdir ./data
sed -i '/DATA_DIR/d' .env
echo 'DATA_DIR=./data' >> .env
pelias compose pull
pelias elastic start
pelias elastic wait
pelias elastic create
pelias download all
pelias prepare all
pelias import all
pelias compose up
Expected behavior The pelias api service runs successfully like the others
Environment (please complete the following information):
$ docker -v Docker version 24.0.4, build 3713ee1
$ docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES fb620b98b9f4 pelias/api:master “./bin/start” 35 seconds ago Restarting (126) 10 seconds ago pelias_api 99a006737abc pelias/placeholder:master “./cmd/server.sh” 35 seconds ago Up 32 seconds 0.0.0.0:4100->4100/tcp, :::4100->4100/tcp pelias_placeholder 5be98070602b pelias/pip-service:master “./bin/start” 35 seconds ago Up 32 seconds 0.0.0.0:4200->4200/tcp, :::4200->4200/tcp pelias_pip-service cb9c1671b4ea pelias/libpostal-service “/bin/wof-libpostal-…” 35 seconds ago Up 32 seconds 0.0.0.0:4400->4400/tcp, :::4400->4400/tcp pelias_libpostal 527685dd9b51 pelias/interpolation:master “./interpolate serve…” 35 seconds ago Up 32 seconds 0.0.0.0:4300->4300/tcp, :::4300->4300/tcp pelias_interpolation 73678339907b pelias/elasticsearch:7.17.9 “/bin/tini – /usr/l…” 9 minutes ago Up 9 minutes 0.0.0.0:9200->9200/tcp, :::9200->9200/tcp, 0.0.0.0:9300->9300/tcp, :::9300->9300/tcp pelias_elasticsearch
$ docker logs --tail 3 --follow --timestamps pelias_api 2023-08-08T17:38:09.136068517Z /bin/bash: ./bin/start: Permission denied 2023-08-08T17:39:09.582053068Z /bin/bash: ./bin/start: Permission denied 2023-08-08T17:40:10.074395564Z /bin/bash: ./bin/start: Permission denied
docker-compose.yml api: image: pelias/api:master container_name: pelias_api user: “${DOCKER_USER}” restart: always environment: [ “PORT=4000” ] ports: [ “4000:4000” ] volumes: - “./pelias.json:/code/pelias.json”
$ docker exec -d pelias_api ls / Error response from daemon: Container fb620b98b9f4aa1728bbfc3ef5f5581f83e7ec7a3fd201de33e36540df64ad28 is restarting, wait until the container is running
$ pelias compose top ERROR: Container fb620b98b9f4aa1728bbfc3ef5f5581f83e7ec7a3fd201de33e36540df64ad28 is restarting, wait until the container is running
About this issue
- Original URL
- State: closed
- Created a year ago
- Reactions: 1
- Comments: 35 (18 by maintainers)
@missinglink Thanks for staying on top of this! Your software helps thousands of people in our community every day. I really appreciate all of your work.
I tried this https://github.com/pelias/docker/issues/318#issuecomment-1671416078 and it works now, thanks @darmentrout you saved me
I have the exact same issue. Running completly fine until it suddenly stopped. Also on ubuntu.
The logs just fill up with
/bin/bash: ./bin/start: Permission deniedotherwise no error.Linux openroute 5.15.0-79-generic #86-Ubuntu SMP Mon Jul 10 16:07:21 UTC 2023 x86_64 x86_64 x86_64 GNU/LinuxI was having the same issue v5.55.0 works fine but no luck with v5.57.0.
When I do a
pelias compose upI get:Error response from daemon: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: "./bin/start": stat ./bin/start: permission denied: unknownI just tried
pelias/api:v5.55.0and the API container is up and I can reach the API’s default web page in the browser.