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

docker-compose sample doesn't set-up fully #261

Closed
AlexKnowsIt opened this issue Dec 20, 2020 · 3 comments
Closed

docker-compose sample doesn't set-up fully #261

AlexKnowsIt opened this issue Dec 20, 2020 · 3 comments
Assignees
Labels
confirmed docker docker related issues
Milestone

Comments

@AlexKnowsIt
Copy link

In case you experience issues with docker image provided by linuxserver.io/papermerge, please open bug report in their repository.

Description
I tried the last days to setup papermerge using docker, but I am having problems with the official image. If I am using the docker image from linuxserver.io I can get the app running without any problems. If I use the example-file version 1.4 from this repository it seems that the the app is not listening on port 8000. This is the output from the command line while setting up:
Migrations for 'core':

papermerge/core/migrations/0035_auto_20201220_1021.py

- Alter field first_name on user

Operations to perform:
Apply all migrations: account, admin, auth, contenttypes, core, dynamic_preferences, dynamic_preferences_users, knox, sessions, sites, socialaccount
Running migrations:
No migrations to apply.
Unknown command: 'drop_triggers'
Type 'manage.py help' for usage.
System check identified no issues (0 silenced).
[2020-12-20 10:22:00,969: INFO/MainProcess] Connected to filesystem://localhost//
[2020-12-20 10:22:01,001: INFO/MainProcess] celery@localhost ready.
[2020-12-20 10:22:04,009: INFO/Beat] beat: Starting...
[2020-12-20 10:23:08,094: INFO/Beat] Scheduler: Sending due task txt2db (papermerge.core.management.commands.worker.txt2db)
[2020-12-20 10:23:08,152: INFO/MainProcess] Received task: papermerge.core.management.commands.worker.txt2db[0fe25b8d-161a-4a70-b1c1-e78a076e2ac1]
[2020-12-20 10:23:08,156: DEBUG/ForkPoolWorker-2] Celery beat: txt2db
[2020-12-20 10:23:08,157: INFO/MainProcess] Received task: papermerge.core.management.commands.worker.txt2db[b1aa02c5-8826-4ce2-9660-05cd2195494d]
[2020-12-20 10:23:08,200: INFO/ForkPoolWorker-2] Task papermerge.core.management.commands.worker.txt2db[0fe25b8d-161a-4a70-b1c1-e78a076e2ac1] succeeded in 0.04409075299918186s: None
[2020-12-20 10:23:08,202: DEBUG/ForkPoolWorker-2] Celery beat: txt2db
[2020-12-20 10:23:08,213: INFO/ForkPoolWorker-2] Task papermerge.core.management.commands.worker.txt2db[b1aa02c5-8826-4ce2-9660-05cd2195494d] succeeded in 0.01100099399627652s: None

What happens
If I am trying to open the web-interface I get a server not found message and there are no indications in the logs, that the request got blocked. It seems like the request is not getting to the server at all.

Info:

  • OS: Ubuntu 20.04 LTS
@AlexKnowsIt AlexKnowsIt added the bug Something isn't working label Dec 20, 2020
@jkuettner
Copy link

I think this is because (probably by mistake) the docker image eugenci/papermerge:1.5.3 was overwritten with the one from eugenci/papermerge-worker:1.5.3.

The images have the same digest

@ciur
Copy link
Owner

ciur commented Dec 20, 2020

@jkuettner, @AlexKnowsIt, right, my mistake :(. Thanks for heads up!
I will fix the issue next week (as part of release 1.5.4).

@ciur ciur added confirmed docker docker related issues and removed bug Something isn't working labels Dec 20, 2020
@ciur ciur added this to the Version 1.5.4 milestone Dec 20, 2020
@ciur
Copy link
Owner

ciur commented Dec 23, 2020

Release 1.5.4 is out.

@ciur ciur closed this as completed Dec 23, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
confirmed docker docker related issues
Projects
None yet
Development

No branches or pull requests

3 participants