Skip to content

Conversation

@manuc66
Copy link
Owner

@manuc66 manuc66 commented Nov 23, 2025

@domse May I ask you to test this ?

@domse
Copy link

domse commented Nov 24, 2025

Thank you for your fast help!
My system is not starting when building the new docker container.
The same config is working fine, when i use the current docker image.

docker run -e IP="<IPScanner>" -e MAIN_COMMAND=adf-autoscan -e PAPERLESS_TOKEN=<TOKEN>
5327021a5e604ae37e6 -e PAPERLESS_POST_DOCUMENT_URL=https://<server>/api/documents/post_document/ -e PGID=1000 -e PUID=1000 node-hp-scan-to
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
cont-init: info: running /etc/cont-init.d/10-adduser
usermod: no changes

User uid:    1000
User gid:    1000
-------------------------------------

cont-init: info: /etc/cont-init.d/10-adduser exited 0
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
Starting
WARNING: NODE_ENV value of 'production' did not match any deployment config file names.
WARNING: See https://github.com/node-config/node-config/wiki/Strict-Mode
WARNING: No configurations found in configuration directory:/app/config
WARNING: To disable this warning set SUPPRESS_NO_CONFIG_WARNING in the environment.
Running with Git commit ID: d27838fa16aadf8b407e96e5a1252b9315d4ced3
Searching device...
^Cs6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped

@manuc66 manuc66 force-pushed the feature/paperless-token-file branch from 405fa4d to ad2b6e5 Compare November 24, 2025 23:24
@domse
Copy link

domse commented Nov 25, 2025

The issue is in master too. Regardless of IP defined in env it is searching for scanners using Bonjour. This doesn't work, so the container restarts. Shall I open another issue for this misbehaviour?

manuc66 added a commit that referenced this pull request Nov 25, 2025
Fix incorrect IP check condition in getDeviceIp function #1468 #1464
@manuc66
Copy link
Owner Author

manuc66 commented Nov 25, 2025

The issue is in master too. Regardless of IP defined in env it is searching for scanners using Bonjour. This doesn't work, so the container restarts. Shall I open another issue for this misbehaviour?

Thanks for reporting, I've introduced the issue and already produced the fix.

@manuc66 manuc66 force-pushed the feature/paperless-token-file branch 2 times, most recently from a809a29 to 35f600d Compare November 25, 2025 22:58
@manuc66 manuc66 force-pushed the feature/paperless-token-file branch from 35f600d to c5ef838 Compare November 25, 2025 22:59
@domse
Copy link

domse commented Dec 3, 2025

It's working as expected. Thank you!

@domse
Copy link

domse commented Dec 3, 2025

There is still a small typo: It should be paperless-password
| --paperless-token-file | File name that contains the paperless token. Required unless--nextcloud-passwordis used. Takes precedence if both are provided.|--paperless-token-file some/path/to/file (no default) |

@manuc66 manuc66 merged commit 03ee884 into master Dec 4, 2025
10 of 11 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants