thehipbot/docker-web2py

web2py Docker files

docker-web2py's Issues

Supervisord permission issue

Howdy,

I tried building your Dockerfile using docker-compose but I keep getting: IOError: [Errno 13] Permission denied: '/var/log/supervisor/supervisord.log' on run.

Regards,
Yusuf

what's the best practice to get my own app running

Thanks for a running and working web2py docker :)

I tried to setup a volume to my app:

volumes:
  - my_fancy_app:/home/www-data/applications/my_fancy_app

But that didn't work. Is there an easy way to add you own web2py app to this docker? I would like to use my_fancy_app as the default app, which involves adding it to routes.py

routers = dict(
    BASE  = dict(default_application='my_fancy_app'),
)

It would be nice if it could be done completely via a environment variables.

Making this work with a valid cert

Hey,

I've tried simply mounted my own cert directory over the top of the /etc/nginx/ssl directory (To replace the .crt and .key file) but the pages aren't accessible when doing this. Is there a quick and easy way to get up and running with a valid cert?

Thanks.

supervisord keeps trying to start nginx, which is trying to run in daemon mode

nginx should be run with daemon mode off under Docker, otherwise supervisord keeps thinking the process has terminated, and tries to restart it.

This results in repeated entries in the supervisor log like;

2016-07-08 15:22:29,985 INFO success: nginx-app entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2016-07-08 15:22:31,489 INFO exited: nginx-app (exit status 1; not expected)
2016-07-08 15:22:32,491 INFO spawned: 'nginx-app' with pid 57

And in the nginx log like:

2016/07/08 15:22:50 [emerg] 63#0: bind() to 0.0.0.0:80 failed (98: Address already in use)
2016/07/08 15:22:50 [emerg] 63#0: bind() to 0.0.0.0:443 failed (98: Address already in use)
2016/07/08 15:22:50 [emerg] 63#0: bind() to 0.0.0.0:80 failed (98: Address already in use)
2016/07/08 15:22:50 [emerg] 63#0: bind() to 0.0.0.0:443 failed (98: Address already in use)
2016/07/08 15:22:50 [emerg] 63#0: bind() to 0.0.0.0:80 failed (98: Address already in use)
2016/07/08 15:22:50 [emerg] 63#0: bind() to 0.0.0.0:443 failed (98: Address already in use)
2016/07/08 15:22:50 [emerg] 63#0: bind() to 0.0.0.0:80 failed (98: Address already in use)
2016/07/08 15:22:50 [emerg] 63#0: bind() to 0.0.0.0:443 failed (98: Address already in use)
2016/07/08 15:22:50 [emerg] 63#0: bind() to 0.0.0.0:80 failed (98: Address already in use)
2016/07/08 15:22:50 [emerg] 63#0: bind() to 0.0.0.0:443 failed (98: Address already in use)
2016/07/08 15:22:50 [emerg] 63#0: still could not bind()

Although a nginx process is running, supervisor keeps trying to start another one.

A work-around is to modify supervisor-app.conf as follows:

[program:nginx-app]
command = /usr/sbin/nginx -g "daemon off;"

This work-around was suggested here: http://stackoverflow.com/questions/33650820/nginx-emerg-bind-to-0-0-0-080-failed-98-address-already-in-use-on-docke/33876214#33876214