Hi, Do you have a link to the reported issue? I tried to find it but I did not manage to find it. I did however found a workaround to change locale during runtime that seem to be working by adding these environment attributes
-e LANG=C.UTF-8 -e LC_ALL=C.UTF-8 On Fri, Aug 25, 2023 at 9:18 AM Kristian Nils Robin Morin < kristian.mo...@trondheim.kommune.no> wrote: > Hi Fernando, > > Thanks for checking and good to know that it looks to be something that > can be fixed. > I have tried using the image you suggested before but have had some > struggles to run it with plugins (probably due to my inexperience with > docker). > (I already have a running task running with Alessandro cristofori at > geosolutions already regarding that) > > On Thu, Aug 24, 2023 at 5:47 PM Fernando Mino < > fernando.m...@geosolutionsgroup.com> wrote: > >> Hi Kristian, >> >> Checking the official docker image (2.23.2) I reproduced the same >> problem. Checking deeper into the container system I found the locale is >> configured as POSIX, hence only basic ASCII characters are allowed: >> >> root@7f66d96fa983:/opt# locale >> LANG= >> LANGUAGE= >> LC_CTYPE="POSIX" >> LC_NUMERIC="POSIX" >> LC_TIME="POSIX" >> LC_COLLATE="POSIX" >> LC_MONETARY="POSIX" >> LC_MESSAGES="POSIX" >> LC_PAPER="POSIX" >> LC_NAME="POSIX" >> LC_ADDRESS="POSIX" >> LC_TELEPHONE="POSIX" >> LC_MEASUREMENT="POSIX" >> LC_IDENTIFICATION="POSIX" >> LC_ALL= >> >> I'll open an issue to report this problem, meanwhile as workaround you >> can try this geoserver image which looks support UTF8 and special >> characters on workspace creation: >> >> docker pull geosolutionsit/geoserver:2.23.2 >> docker run -it -p8080:8080 geosolutionsit/geoserver:2.23.2 >> >> Regards, >> >> Fernando Mino >> >> == >> >> GeoServer Professional Services from the experts! >> >> Visit http://bit.ly/gs-services-us for more information. >> >> == >> >> Fernando Mino >> >> Software Engineer >> >> @fmy2kec >> >> GeoSolutions Group >> phone: +39 0584 962313 >> >> fax: +39 0584 1660272 >> >> https://www.geosolutionsgroup.com/ >> >> http://twitter.com/geosolutions_it >> >> ------------------------------------------------------- >> >> Con riferimento alla normativa sul trattamento dei dati personali (Reg. >> UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si >> precisa che ogni circostanza inerente alla presente email (il suo >> contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è >> riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il >> messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra >> operazione è illecita. Le sarei comunque grato se potesse darmene notizia. >> >> This email is intended only for the person or entity to which it is >> addressed and may contain information that is privileged, confidential or >> otherwise protected from disclosure. We remind that - as provided by >> European Regulation 2016/679 “GDPR” - copying, dissemination or use of this >> e-mail or the information herein by anyone other than the intended >> recipient is prohibited. If you have received this email by mistake, please >> notify us immediately by telephone or e-mail. >> >> >> On Thu, Aug 24, 2023 at 8:06 AM Kristian Nils Robin Morin via >> Geoserver-users <geoserver-users@lists.sourceforge.net> wrote: >> >>> Hi, >>> >>> I am implementing geoserver to run as a docker container. But geoserver >>> fail to start due to unmappable characters. This error also occurs if I >>> start geoserver with a new data_dir and try to save a style or workspace >>> with a name with special character (åæø). This has not been an issue when >>> geoserver has been deployed not using docker. >>> Does anyone have similar issues or found a way to solve it? I suppose >>> the issue is how the image was built? >>> >>> Caused by: java.nio.file.InvalidPathException: Malformed input or input >>> contains unmappable characters: >>> /opt/geoserver_data/workspaces/kpa_forslag/styles/KpBestemmelseOmr��de.xml.xml >>> >>> >>> _______________________________________________ >>> Geoserver-users mailing list >>> >>> Please make sure you read the following two resources before posting to >>> this list: >>> - Earning your support instead of buying it, but Ian Turton: >>> http://www.ianturton.com/talks/foss4g.html#/ >>> - The GeoServer user list posting guidelines: >>> http://geoserver.org/comm/userlist-guidelines.html >>> >>> If you want to request a feature or an improvement, also see this: >>> https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer >>> >>> >>> Geoserver-users@lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/geoserver-users >>> >> > > -- > Med hilsen > > *Kristian Morin* > Geodata, systemutvikling > Enhet for kart og arkitektur > Sentralbord: 72 54 25 00 > Telefon: 90539229 > > > > -- Med hilsen *Kristian Morin* Geodata, systemutvikling Enhet for kart og arkitektur Sentralbord: 72 54 25 00 Telefon: 90539229
_______________________________________________ Geoserver-users mailing list Please make sure you read the following two resources before posting to this list: - Earning your support instead of buying it, but Ian Turton: http://www.ianturton.com/talks/foss4g.html#/ - The GeoServer user list posting guidelines: http://geoserver.org/comm/userlist-guidelines.html If you want to request a feature or an improvement, also see this: https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
