Open michaelschefczyk opened 3 years ago
Hi, I am seeing same error:
[2021-07-11 09:06:36 +0000] [8] [INFO] Starting gunicorn 19.10.0
[2021-07-11 09:06:36 +0000] [8] [INFO] Listening at: http://0.0.0.0:5000 (8)
[2021-07-11 09:06:36 +0000] [8] [INFO] Using worker: sync
[2021-07-11 09:06:36 +0000] [16] [INFO] Booting worker with pid: 16
[2021-07-11 09:06:37 +0000] [16] [ERROR] Exception in worker process
Traceback (most recent call last):
File "/usr/local/lib/python2.7/site-packages/gunicorn/arbiter.py", line 586, i n spawn_worker
worker.init_process()
File "/usr/local/lib/python2.7/site-packages/gunicorn/workers/base.py", line 1 35, in init_process
self.load_wsgi()
File "/usr/local/lib/python2.7/site-packages/gunicorn/workers/base.py", line 1 44, in load_wsgi
self.wsgi = self.app.wsgi()
File "/usr/local/lib/python2.7/site-packages/gunicorn/app/base.py", line 67, i n wsgi
self.callable = self.load()
File "/usr/local/lib/python2.7/site-packages/gunicorn/app/wsgiapp.py", line 52 , in load
return self.load_wsgiapp()
File "/usr/local/lib/python2.7/site-packages/gunicorn/app/wsgiapp.py", line 41 , in load_wsgiapp
return util.import_app(self.app_uri)
File "/usr/local/lib/python2.7/site-packages/gunicorn/util.py", line 350, in i mport_app
import(module)
File "/app/syncserver/wsgi_app.py", line 2, in
Did you fix guys this issue? I had working container before but yesterday I did clean install of system and now I can't manage it to work while I'm using clean docker image :/
I had this issue - re-read the docs and realised the issue...
There is experimental support for running the server inside a Docker container. The docker image runs with UID/GID 1001/1001.
A quick id 1001
and chown
fixed the issue.
I had this issue - re-read the docs and realised the issue...
There is experimental support for running the server inside a Docker container. The docker image runs with UID/GID 1001/1001.
A quick
id 1001
andchown
fixed the issue.
within container? or where?
I had this issue - re-read the docs and realised the issue...
There is experimental support for running the server inside a Docker container. The docker image runs with UID/GID 1001/1001.
A quick
id 1001
andchown
fixed the issue.within container? or where?
On the host file system, or use a different database address (MySQL might work fine with SQLAlchemy)
any updates on this issue ? I'm still getting the error unable to open database file
when using a volume with docker-compose
I give up with this official Docker, I use instead Docker created by Docker employee: https://registry.hub.docker.com/r/crazymax/firefox-syncserver/ https://github.com/crazy-max/docker-firefox-syncserver Works fine since then (except somehow not works on phone, not sure why).
Thank's for your answer. I gave it a try and managed to make it work with MariaDB instead of sqlite.
the mozilla/syncserver:latest
same
Dear All,
I did run this for many months based on internal docker builds - thanks!! The last running build was a week old. A new build does no longer seem to run, probably based on python 2.7 issues. The log shows:
File "/usr/local/lib/python2.7/site-packages/sqlalchemy/pool/base.py", line 639, in __connect connection = pool._invoke_creator(self) File "/usr/local/lib/python2.7/site-packages/sqlalchemy/engine/strategies.py", line 114, in connect return dialect.connect(*cargs, *cparams) File "/usr/local/lib/python2.7/site-packages/sqlalchemy/engine/default.py", line 453, in connect return self.dbapi.connect(cargs, **cparams) OperationalError: (sqlite3.OperationalError) unable to open database file (Background on this error at: http://sqlalche.me/e/e3q8)
That does not seem to have anything to do with my mysql setup because this container https://github.com/crazy-max/docker-firefox-syncserver does run when putting the same sqlalchemy string in its environment variable.
Regards,
Michael Schefczyk