codesuki / ecs-nginx-proxy

Reverse proxy for AWS ECS. Lets you address your docker containers by sub domain.
MIT License
98 stars 23 forks source link

The container can not start: error "task: non-zero exit (1)" #19

Closed thmspl closed 3 years ago

thmspl commented 7 years ago

I'm trying to set up the nginx proxy on my Amazon AWS Docker instance together with a pimcore instance. This is my compose file:

version: '3.4'

services:  
  nginx-proxy:
    image: codesuki/ecs-nginx-proxy
    ports:
      - "80:80"
  pimcore-jcii:
    image: ****/pimcore5:current
    ports:
      - "8000:80"
    links:
      - "db"
    volumes:
      - efs-storage:/data
  db:
    image: mariadb
    restart: always
    ports:
      - "3306:3306"

volumes:
  efs-storage:
    driver: cloudstor:aws
    driver_opts:
      backing: shared

If I deploy this stack the nginx proxy container can not start. It appears the following error message: task: non-zero exit (1)

What am I doing wrong?

codesuki commented 7 years ago

Are you using ECS?

thmspl commented 7 years ago

@codesuki Yes, I'm using ECS.

codesuki commented 7 years ago

Hard to diagnose from this. Do the ECS machines have the needed permissions? Is there any log output? In many cases ecs-nginx-proxy should log some kind of error. If you could post the log output maybe we can find a solution.