paperless-ngx: running stack is shown as inactive about dockge

[JarlMorgennebel]

[djismgaming]

Have you tried without the version: "3.4" line?
It has been removed from compose anyways.

[pusi77]

I have the same problem, removing the version line does not fix it.
I also see a "paperless" stack active, but not managed by dockge (and I have no other paperless stack):

[JarlMorgennebel]

Same here.

No change on the version-line, seeing an additional paperless stack which changes status as well.

[truthsword]

Not an issue here

[JarlMorgennebel]

Is this paperless or Paperless-ngx? ⁣BlueMail for Android herunterladen ​ Am 9. Apr. 2024, 17:28, um 17:28, truthsword ***@***.***> schrieb:

…

Not an issue here  -- Reply to this email directly or view it on GitHub: #474 (comment) You are receiving this because you authored the thread. Message ID: ***@***.***>

[truthsword]

Is this paperless or Paperless-ngx?

ngx ... same as the thread

Your compose file seems off. Maybe that's the source of your issue.

[xtr3-m3]

I changed the name in the .env file COMPOSE_PROJECT_NAME=paperless in my docker-compose folder from paperless to paperless-ngx (thats the name of my container in the docker-compose.yml). After deleting the containers and new docker compose up -d its fine now in dockge!

[truthsword]

Just FYI... but you have other issues ... for some reason you have defined docker volumes (which aren't used) while you also have defined bind mount volumes. You also have a type on a docker volume, but as that presumably is not used, it is just noise. A check of your compose file using docker compose config should have flagged these things. Good luck.

[xtr3-m3]

Yes , i had unused docker volumes. I removed them now and reverted the .env back to paperless and created new containers. Same Output with the inactive paperless-ngx in dockge. I changed it back to paperless-ngx in the .env and its now working again. At least i have a cleaner compose file now..