-
Notifications
You must be signed in to change notification settings - Fork 82
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
Warning since last update #14
Comments
These warnings were introduced with Arksine/moonraker@3a384e6. Looking at the underlying function, it seems that Moonraker gets these paths from klippy via the socket and there currently is no way of overwriting these locations within -Markus |
I'll reopen this, as i might have a possible solution to monkey patch the running Moonraker instance to contain the requested directories. -Markus |
Have a look at this Branch: moonraker-init Imho this is just a dirty hack. |
Well, this sounds better than my approach: I was about to just create the directories at their default location (where they make absolutely no sense). I will try that soon. |
With fluidd-core/fluidd#505 this is now also present in fluidd. |
Do you still need me to test it? It's not as easy to install as I would have to change my docker-compose file. So, if you are convenient it doesn't break anything I would wait until this comes to upstream. However, if you need someone to test it, I can try. |
It would be great if you could give it a try. -Markus |
I just tried it out. If I didn't make a mistake, the warnings are still there. Maybe I misconfigured something? |
Mind sharing your compose file?
Have any klipper files been copied to the moonraker container?
|
Here's my compose file
I also would like to provide docker logs, however, after pulling the images again, I cannot get moonraker to start.
However, Here's the other output:
Seems nothing has been created, or has it? Here are all logs
|
Your compose file looks fine to me. Here are a few things you could try. Option 1: (preferred) Trigger the init Service again
Option 2: Manually Copy Files
On an unrelated note, I noticed that the |
hm. I use my home server which runs a amd64 architecture. I can still try to put the directories where Moonraker expects them. It just doesn't seem "correct" but, maybe that's the easiest way... Still have to try to start init-moonraker manually. Or maybe it would make sense to raise a feature request in the moonraker repo to get the possibility to configure the path? |
The options I mentioned above are meant as troubleshooting steps, as I could not reproduce your described behaviour. Manually copying the Files is not the correct long-term solution. At the moment I would like to bother the Maintainers of the packaged software as little as possible as long as there are viable Workarounds for running their projects in Docker. |
Sorry to jump in but i have similar problems after updating to latest docker 20.10.14 today, everything worked perfectly before the update. And i have the following errors after replacing my |
@gminadak please share your moonraker.cfg and a full moonraker log. |
@mkuf thank you for your reply |
@gminadak Lines 9 to 10 in 081cfaa
Also, make sure to use mkuf/moonraker:4b27e5e or later, as described in the v0.5.0 Releasenotes |
@mkuf by adding The PolicyKit warnings have gone, after some researching i come across this on GitHub Thank you for your help. |
Thanks for pointing this out. I did not consider this when implementing the features for v0.5.0. Did you test the moonraker-init branch to get rid of the directory warnings, @gminadak? |
@mkuf
Edit forgot to mention the container ID
|
So the init-moonraker container failed. On which architecture are you running? |
This is better i think |
The errors in
Which docker compose version are you using? |
gminadak@linux-server:~/prind-init$ docker-compose version |
Thats quite old. v1 might handle container creation in a different way, so that moonraker does not exist at the time we try to copy files into it. |
I'm still wondering how did i miss this step. gminadak@linux-server:~/prind-init$ docker-compose version gminadak@linux-server:~/prind-init$ docker-compose --profile fluidd up -d [+] Running 9/9
|
I gave this a try on my printer, which is equipped with a fairly old udoo quad. So I went ahead and mounted |
Since my recent pull I get these Warnings in Mainsail
I couldn't tack down the source of this message but I think that they are again imposed by recent changes in Moonraker.
The text was updated successfully, but these errors were encountered: