-
Notifications
You must be signed in to change notification settings - Fork 423
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
backup-restore-plugin failing with permissions issues #528
Comments
You haven't specified where you are trying to create the backup in. You can try to place it in temp and also what user owns the files there |
Thanks NyakudyaA, Yes I've tried in /tmp, /opt/geoserver/data_dir and also creating a folder /backups in the root. None work correctly. |
Will take a look when I am near a PC |
Will report this upstream and see if they have a fix. |
Thanks NyakudyaA! |
Any progress with this NyakudyaA? Did you have an upstream issue we can follow? |
Opened an issue upstream but they closed it saying they don't investigate things that are running in docker, will check this over the weekend |
Any movement on this NyakudyaA? |
@genebobmiller Have you tried with image 2.23.1 |
@NyakudyaA There is no such image on dockerhub. |
There must be something wrong with the github action. I will investigate and also test the plugin with the new version |
Issue still exists in 2.23.1 |
Seems to be having trouble writing to a temporary folder...
In kartoza/geoserver:2.17.0 the backup process successfully created these folders:
But in kartoza/geoserver:2.23.1 the backup process fails because it's attempting to create these folders in the root of the file system and getting permission denied:
|
The issue referred to is GEOS-10990. Is it really necessary to run as root (which is discouraged for security reasons) for backup-restore? It looks like the plugin might be misconfigured if it tries to write |
Yes, @hbruch That's a workaround, unfortunately, I am not a Java developer and to debug what is happening during runtime configuration. |
What is the bug or the crash?
Permissions issues are causing the backup-restore-plugin to fail.
This issue is not present in 2.17 so I assume it's caused by the permissions change made in 2.18 when we moved away from root ownership.
Steps to reproduce the issue
Enable the backup-restore-plugin via ENV var:
Click on Data->Backup & Restore.
Creating a backup shows warnings:
and restoring the backup fails with errors:
Versions
2.23.0
Additional context
Not present in 2.17
The text was updated successfully, but these errors were encountered: