Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Production setup runs into endless loop #57

Closed
glor opened this issue Dec 8, 2018 · 4 comments
Closed

Production setup runs into endless loop #57

glor opened this issue Dec 8, 2018 · 4 comments

Comments

@glor
Copy link

glor commented Dec 8, 2018

I followed the instructions under 'Quick Development Setup'
But all containers except redis seam to be stuck in an endless restart loop:
https://asciinema.org/a/9SXQkcstckOkMumkdxDltgpfc

Setup: Manjaro Linux (behaves nearly the same as arch linux), my usual working machine.
Did I do something wrong or is it a bug?

@glor
Copy link
Author

glor commented Dec 8, 2018

I could reproduce a similar problem on a different setup (Ubuntu 16.04, relatively fresh installation). Differently only one image is stuck in an endless loop:

CONTAINER ID        IMAGE               COMMAND                  CREATED             STATUS                          PORTS               NAMES
593bea5e86b7        judge0/api          "/bin/sh -c 'rm -f..."   27 minutes ago      Restarting (1) 13 minutes ago                       cloud_api_1
dadc04215830        judge0/api          "rails resque:work"      27 minutes ago      Up 27 minutes                   3000/tcp            cloud_worker_1
71166e0c18de        redis               "docker-entrypoint..."   27 minutes ago      Up 27 minutes                   6379/tcp            cloud_redis_1
673a928023a2        postgres            "docker-entrypoint..."   41 minutes ago      Up 41 minutes                   5432/tcp            cloud_db_1

@hermanzdosilovic
Copy link
Member

Hi @glor,

sorry for the delayed response. Please take a look at this issue: #56.

@glor
Copy link
Author

glor commented Jan 1, 2019

Actually my docker-compose.yml already sais postgres:9.6.5.
Or did you mean something else?

$ cat docker-compose.yml 
version: '2'
services:
  api:
    image: judge0/api
    env_file: judge0-api.conf
    ports:
      - "3000:3000"
    privileged: true
    restart: always

  worker:
    image: judge0/api
    env_file: judge0-api.conf
    command: rails resque:work
    privileged: true
    restart: always

  db:
    image: postgres:9.6.5
    env_file: judge0-api.conf
    volumes:
      - ./srv/postgres-data:/var/lib/postgresql/data/
    restart: always

  redis:
    image: redis:4.0.9
    command: redis-server --appendonly yes
    volumes:
      - ./srv/redis-data:/data
    restart: always

@hermanzdosilovic
Copy link
Member

Can you please do the following:

$ docker-compose down

And then remove ./srv folder. Warning! This will delete your Judge0 data you currently have.

And after that try again with the Quick Production Setup.

Please let me know if I can help you more!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants