Docker installation fails

(Please include your Gramps version and Operating System)

I have attempted to install Grampsweb via the droplet on DO, and via the compose file located here: https://raw.githubusercontent.com/gramps-project/gramps-web-docs/main/examples/docker-compose-letsencrypt/docker-compose.yml.

Both attempts have failed to run first-run script. Both have incurred heavy CPU usage.

Here is the log from the latest attempt (docker droplet) :

root@grampsweb:~# docker compose logs --tail 100 grampsweb
grampsweb | File “/venv/lib/python3.13/site-packages/click/core.py”, line 1552, in main
grampsweb | rv = self.invoke(ctx)
grampsweb | File “/venv/lib/python3.13/site-packages/click/core.py”, line 2032, in invoke
grampsweb | return _process_result(sub_ctx.command.invoke(sub_ctx))
grampsweb | ~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^
grampsweb | File “/venv/lib/python3.13/site-packages/click/core.py”, line 2032, in invoke
grampsweb | return _process_result(sub_ctx.command.invoke(sub_ctx))
grampsweb | ~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^
grampsweb | File “/venv/lib/python3.13/site-packages/click/core.py”, line 1415, in invoke
grampsweb | return ctx.invoke(self.callback, **ctx.params)
grampsweb | ~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
grampsweb | File “/venv/lib/python3.13/site-packages/click/core.py”, line 910, in invoke
grampsweb | return callback(*args, **kwargs)
grampsweb | File “/venv/lib/python3.13/site-packages/click/decorators.py”, line 34, in new_func
grampsweb | return f(get_current_context(), *args, **kwargs)
grampsweb | File “/app/src/gramps_webapi/main.py”, line 239, in migrate_db
grampsweb | subprocess.run(cmd, env=env, check=True)
grampsweb | ~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^
grampsweb | File “/usr/lib/python3.13/subprocess.py”, line 577, in run
grampsweb | raise CalledProcessError(retcode, process.args,
grampsweb | output=stdout, stderr=stderr)
grampsweb | subprocess.CalledProcessError: Command ‘[’/venv/bin/python3’, ‘-m’, ‘alembic’, ‘upgrade’, ‘head’]’ returned non-zero exit status 255.
grampsweb | INFO [alembic.runtime.migration] Context impl SQLiteImpl.
grampsweb | INFO [alembic.runtime.migration] Will assume non-transactional DDL.
grampsweb | ERROR [alembic.util.messaging] Requested revision 9c4d2e7a5b18 overlaps with other requested revisions a8e57fe0d82e
grampsweb | FAILED: Requested revision 9c4d2e7a5b18 overlaps with other requested revisions a8e57fe0d82e
grampsweb | Traceback (most recent call last):
grampsweb | File “”, line 198, in _run_module_as_main
grampsweb | File “”, line 88, in _run_code
grampsweb | File “/app/src/gramps_webapi/main.py”, line 489, in
grampsweb | cli(
grampsweb | ~~~^
grampsweb | prog_name=“python3 -m gramps_webapi”
grampsweb | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
grampsweb | ) # pylint:disable=no-value-for-parameter,unexpected-keyword-arg
grampsweb | ^
grampsweb | File “/venv/lib/python3.13/site-packages/click/core.py”, line 1631, in call
grampsweb | return self.main(*args, **kwargs)
grampsweb | ~~~~~~~~~^^^^^^^^^^^^^^^^^
grampsweb | File “/venv/lib/python3.13/site-packages/click/core.py”, line 1552, in main
grampsweb | rv = self.invoke(ctx)
grampsweb | File “/venv/lib/python3.13/site-packages/click/core.py”, line 2032, in invoke
grampsweb | return _process_result(sub_ctx.command.invoke(sub_ctx))
grampsweb | ~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^
grampsweb | File “/venv/lib/python3.13/site-packages/click/core.py”, line 2032, in invoke
grampsweb | return _process_result(sub_ctx.command.invoke(sub_ctx))
grampsweb | ~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^
grampsweb | File “/venv/lib/python3.13/site-packages/click/core.py”, line 1415, in invoke
grampsweb | return ctx.invoke(self.callback, **ctx.params)
grampsweb | ~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
grampsweb | File “/venv/lib/python3.13/site-packages/click/core.py”, line 910, in invoke
grampsweb | return callback(*args, **kwargs)
grampsweb | File “/venv/lib/python3.13/site-packages/click/decorators.py”, line 34, in new_func
grampsweb | return f(get_current_context(), *args, **kwargs)
grampsweb | File “/app/src/gramps_webapi/main.py”, line 239, in migrate_db
grampsweb | subprocess.run(cmd, env=env, check=True)
grampsweb | ~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^
grampsweb | File “/usr/lib/python3.13/subprocess.py”, line 577, in run
grampsweb | raise CalledProcessError(retcode, process.args,
grampsweb | output=stdout, stderr=stderr)
grampsweb | subprocess.CalledProcessError: Command ‘[’/venv/bin/python3’, ‘-m’, ‘alembic’, ‘upgrade’, ‘head’]’ returned non-zero exit status 255.
grampsweb | INFO [alembic.runtime.migration] Context impl SQLiteImpl.
grampsweb | INFO [alembic.runtime.migration] Will assume non-transactional DDL.
grampsweb | ERROR [alembic.util.messaging] Requested revision 9c4d2e7a5b18 overlaps with other requested revisions a8e57fe0d82e
grampsweb | FAILED: Requested revision 9c4d2e7a5b18 overlaps with other requested revisions a8e57fe0d82e
grampsweb | Traceback (most recent call last):
grampsweb | File “”, line 198, in _run_module_as_main
grampsweb | File “”, line 88, in _run_code
grampsweb | File “/app/src/gramps_webapi/main.py”, line 489, in
grampsweb | cli(
grampsweb | ~~~^
grampsweb | prog_name=“python3 -m gramps_webapi”
grampsweb | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
grampsweb | ) # pylint:disable=no-value-for-parameter,unexpected-keyword-arg
grampsweb | ^
grampsweb | File “/venv/lib/python3.13/site-packages/click/core.py”, line 1631, in call
grampsweb | return self.main(*args, **kwargs)
grampsweb | ~~~~~~~~~^^^^^^^^^^^^^^^^^
grampsweb | File “/venv/lib/python3.13/site-packages/click/core.py”, line 1552, in main
grampsweb | rv = self.invoke(ctx)
grampsweb | File “/venv/lib/python3.13/site-packages/click/core.py”, line 2032, in invoke
grampsweb | return _process_result(sub_ctx.command.invoke(sub_ctx))
grampsweb | ~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^
grampsweb | File “/venv/lib/python3.13/site-packages/click/core.py”, line 2032, in invoke
grampsweb | return _process_result(sub_ctx.command.invoke(sub_ctx))
grampsweb | ~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^
grampsweb | File “/venv/lib/python3.13/site-packages/click/core.py”, line 1415, in invoke
grampsweb | return ctx.invoke(self.callback, **ctx.params)
grampsweb | ~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
grampsweb | File “/venv/lib/python3.13/site-packages/click/core.py”, line 910, in invoke
grampsweb | return callback(*args, **kwargs)
grampsweb | File “/venv/lib/python3.13/site-packages/click/decorators.py”, line 34, in new_func
grampsweb | return f(get_current_context(), *args, **kwargs)
grampsweb | File “/app/src/gramps_webapi/main.py”, line 239, in migrate_db
grampsweb | subprocess.run(cmd, env=env, check=True)
grampsweb | ~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^
grampsweb | File “/usr/lib/python3.13/subprocess.py”, line 577, in run
grampsweb | raise CalledProcessError(retcode, process.args,
grampsweb | output=stdout, stderr=stderr)
grampsweb | subprocess.CalledProcessError: Command ‘[’/venv/bin/python3’, ‘-m’, ‘alembic’, ‘upgrade’, ‘head’]’ returned non-zero exit status 255.

Here is the ps:

root@grampsweb:~# docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
9ffacbeb12ab Package grampsweb · GitHub “/docker-entrypoint.…” 46 minutes ago Up 1 second 5000/tcp grampsweb_celery
87ea100b86f4 nginxproxy/acme-companion “/bin/bash /app/entr…” 46 minutes ago Up 39 minutes nginx-proxy-acme
d8cf3e71b832 Package grampsweb · GitHub “/docker-entrypoint.…” 47 minutes ago Up 1 second 5000/tcp grampsweb
f1e92abc00df valkey/valkey:8-alpine “tini – docker-entr…” 47 minutes ago Up 39 minutes 6379/tcp grampsweb_redis
af8608043213 nginxproxy/nginx-proxy “/app/docker-entrypo…” 47 minutes ago Up 39 minutes 0.0.0.0:80->80/tcp, [::]:80->80/tcp, 0.0.0.0:443->443/tcp, [::]:443->443/tcp nginx-proxy

Any thoughts on next steps?

Hi,

could it be your droplet has too little RAM/CPU?

Dedicated AMD V5 / 2 vCPUs / 4 GB RAM / 50 GB Disk

I couldn’t find requirements anywhere.

I have - quite some time ago - seen this behaviour with the grampsweb and grampsweb_celery containers keeping restarting.
I don’t remember exactly what caused this error, but it was a misconfiguration in the docker-compose.yaml file.
So I think you must examine the docker-compose.yaml
If you also are using a config.cfg, this might also be examined.