support podman based development without permission issues
#1421
Comments
|
Thanks for the thurough report ^^ Okay, I invested a bit of time today to speed this up. Tip Some of the issues are likely permission issues between
The first build using cargo is slow. Because Speed, Compile-times and safety are not great friends, Rust chose to sacrifice Compile-time. It might be noted that local dependencies => There is not much that can be done in this department other than waiting for language-features (polonius,cranelift,paralell-frontend,...) to make this suck less. I have done a few optimizations today, but those are likely not major
Seems weird. This might be related to running
It might be that the webclient Dockerfile is not currently capable of being run with a rootless user. I will have to debug this more in detail.
That endless loop means that the server has "successfully" initialized the database and is now trying to sync the calendar. About the Meilisearch
Seems to be another instance of the issue noted above with the permission difference between
Honestly, for an initial build, that is likely not achievable with the current toolchain.
|
|
@CommanderStorm Thanks for your effort! It would be awesome, if it would work with podman as well, but I would consider this a feature request then. Feel free to change this issue accordingly. For the startup time: the 5min where just an arbitrary time as it was not clear to me when it is finished now, if it's <10min this would of course not be ideal, but having to wait 25min until this build finishes and in between having times where the log output does not change, but this Javascript Vue.js/Nitro stuff does whatever on earth that takes so long and does not give any progress, does not raise one's confidence in that I am actually on the right way to get a development setup running and makes it really hard to develop, as one is only waiting for these builds... I don't want to interact with the calendar. I just wanted to get a local setup running to be able to iteratively figure out the coordinates that would be needed for the rooms. If you would have guidance on what would be needed for that, this would probably be most helpful. |
you can append |
CommanderStorm
changed the title
podman based development without permission issues
CommanderStorm
added
feature
Ok, thank you, but how do I see where the location of the coordinates in the URL is and what is this second marker for that appears in this debug mode? |
|
Ah sorry, forgot to tell: |
|
FYI: I think I have improved the setup significantly, should be much more pleasant. |
Describe the bug
Just running
podman compose -f docker-compose.local.yml up --buildwhen trying to run the the server locally on a laptop with plenty of system resources takes 25min until it's in a state ofmeilisearchrunning, but nothing is changing anymore, but rust consuming 100% CPU for the whole time from starting the build, if rust and cargo are not installed on the local system.If rust and cargo are installed on the local system, this tremendous resource usage by rust is gone, but Node.js now uses significant amounts of ram (but by fare not everything that is available, so in case this is the limiting factor, I would for one question why it needs that much and if it does why it does not use it, if available to speed it up) and takes forever, before after about 25min again ending in a state where
meilisearchandapiin turns logging the same HTTP requests and errors indefinitely and nothing is changing anymore.Always showing up, no matter what I do
If rust and cargo are installed, Node.js then produces this error, despite Python 3.12 being installed on the host system by default and Node.js beeing installed on the Host as well
And it end in an endless loop of
Also when trying to the osm-download
via these commands
then in the hope this would solve the errors as one cannot run it before starting the build one still only gets an error
To Reproduce
Steps to reproduce the behavior:
Just try to run
podman compose -f docker-compose.local.yml up --buildas per install instructions. Podman should be fully compatible to docker.Expected behavior
It either produces a running working server directly or finishes in <5min and I can start the server in a different way.
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: