jpbruinsslot
commented
8 years ago @Pharetra I've updated the project. If you like, you can checkout the latest master branch, it might solve the problems you were having.
Closed ghost closed 8 years ago
jpbruinsslot
commented
8 years ago @Pharetra I've updated the project. If you like, you can checkout the latest master branch, it might solve the problems you were having.
ghost
commented
8 years ago Thanks for the update. The sample project worked out of the box, but I still have some issues with adding my own project. This is repeated constantly after entering docker-compose up:
webapp_1 | *** has_emperor mode detected (fd: 5) ***
webapp_1 | [uWSGI] getting INI configuration from /etc/uwsgi/django-uwsgi.ini
webapp_1 | *** Starting uWSGI 2.0.11.1 (64bit) on [Sun Jan 10 20:42:52 2016] ***
webapp_1 | compiled with version: 4.9.2 on 10 January 2016 20:41:18
webapp_1 | os: Linux-3.19.0-25-generic #26~14.04.1-Ubuntu SMP Fri Jul 24 21:16:20 UTC 2015
webapp_1 | nodename: 7fd6c45ff449
webapp_1 | machine: x86_64
webapp_1 | clock source: unix
webapp_1 | pcre jit disabled
webapp_1 | detected number of CPU cores: 2
webapp_1 | current working directory: /
webapp_1 | detected binary path: /usr/local/bin/uwsgi
webapp_1 | setgid() to 108
webapp_1 | setuid() to 104
webapp_1 | chdir() to /srv/vms/
webapp_1 | chdir(): Permission denied [core/uwsgi.c line 2581]
webapp_1 | chdir(): Permission denied [core/uwsgi.c line 1603]
webapp_1 | Sun Jan 10 20:42:52 2016 - [emperor] curse the uwsgi instance /etc/uwsgi/django-uwsgi.ini (pid: 21)
webapp_1 | Sun Jan 10 20:42:55 2016 - [emperor] removed uwsgi instance /etc/uwsgi/django-uwsgi.ini@Pharetra Glad to hear that the sample project worked! It seems that uWSGI doesn't have permission to access the folder /srv/vms/. uWSGI is run by the django user and this user is added in the Dockerfile of the webapp. Perhaps the following line has to be updated: https://github.com/erroneousboat/docker-django/blob/master/webapp/Dockerfile#L21
RUN chown -R django:django /srv/vms
It could also be because of folder permissions of the local file system for that folder and problems with mounting that folder inside the container. You could try to comment out the following line in the docker-compose.yml file: https://github.com/erroneousboat/docker-django/blob/master/docker-compose.yml#L31
ghost
commented
8 years ago @erroneousboat The chown line was already updated. Commenting out the line in docker-compose.yml didn't work, sadly.
Hey,
I'm trying to run the container, but this is what my terminal outputs after entering
$ docker-compose up:I have no idea why the datastore exited. I did check of /etc/my_init,d/setup.sh actually exists however, and the answer is no. The entire my_init.d folder is missing, actually. Any ideas on how to solve this?