Closed mwallschlaeger closed 9 months ago
There is a lot of work going on regarding GeoNode bootstrap and configuration of GeoServer, memcached, monitoring, geoip, etc.
We would have to revise settings (new/changed/orphaned) once 4.2.0 is ready
Just for the records, I gave it a try few days ago with the master branch, apart from the variables OGC_SERVER_DEFAULT_PASSWORD and OGC_SERVER_DEFAULT_USER I had to tweak with the following function which retrieves the port exposed by container https://github.com/GeoNode/geonode/blob/80e2bbfef601ae3c209950f6c659c5976bd1c4f1/tasks.py#L481
The python docker SDK is failing in minikube context.
Yeah, your right about the python docker SDK used in the tasks.py. This will make more problems in kubernetes environments running on other container engines. We need to think about this at some point in depth. I'm gonna open an issue for the docker SDK.
Thanks for your remarks, at this point. IF you have time feel free to open an PR on this Issue.
Bug Description
running an image build after geonode release 4.1.2 breaks the geonode container init process. This is related to changes in tasks.py and the deletion of some variables inside the default settings.py. This leads to a stop at entrypoint step to run set the geoserver admin password and further this breaks all furhter steps as they do not get executed.
Error output:
Additional Information
Any additional information or context that may be helpful in resolving the bug.