-
Notifications
You must be signed in to change notification settings - Fork 8
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
Fresh install crash #17
Comments
Hi, I suspect this is due to a problem with the mounted config files. Please make sure the files I added a section to the readme to clarify this. |
Hi, thanks for the tip. I figured out that I was missing an importent point:
|
I will need a bit more info to help you. Can you rerun with verbose enabled and paste the output? |
Sorry for the delay. I just get this error with verbose on, a lot of times per seconds:
The remarkable-pocket file looks kind of like this:
|
I have found the problem: the program waits to stdin, which docker compose doesn't set up by default. It works with docker CLI because in your example, you use the Because you use a webserver to handle the pocket connection, would it be possible to do the same for the reMarkable one-time password? |
Thanks for debugging this one. I didn't consider the auth flow for docker-compose. It seems something like Wrt to your suggestion: the Pocket auth flow uses oath, making a browser a necessity. I'd rather not change the Remarkable auth flow to accommodate the docker-compose usecase. I think the easiest solution is to use the |
Your solution should work for docker compose. However, the constraint of having to copy and paste the code is breaking every tentative to automate the start-up. If not with the webserver, maybe provide an alternative way with a environment variable? If it's set, no need to ask it via stdin :) |
It's not possible to automate the Pocket oauth flow, regardless of how the Remarkable cloud code is provided. I don't see how providing the code through an env var would solve this. What would you like to automate? The way I see it you authenticate once manually to create the config files, and then you can automate the start-up any way you like. |
I'll close this as a solution now exists. |
Hi,
Wanted to test that using docker-compose, but it crash at first run.
Here is my docker-compose:
Docker version:
20.10.21, build baeda1f82a
Docker compose: installed as a plugin (v2)
I couldn't guess much from the standard error. The debug logs says it's not connected to the internet, but it is.
But I cannot debug further, as I haven't found the
Dockerfile
. Where is it?Standard error output
Debug error output: https://pastebin.com/ZXGwrW0n
The text was updated successfully, but these errors were encountered: