Wouter Born

I think that a mid 2023 release of OH 4 using Java 17 (see [discussion](https://github.com/orgs/openhab/teams/architecture-council/discussions/15)) means that this may get merged after OH 3.4 is released in December 2022.

Is this still an issue in OH 3.1?

It already runs openHAB as a non root "openhab" user that you can specify using the USER_ID and GROUP_ID env vars. See: https://github.com/openhab/openhab-docker#environment-variables

Yes it does some initial setup as "root" so users can use a custom UID/GID for the "openhab" user, e.g. so it matches those of a user on the host....

Yes that makes sense to also support such a setup for users who prefer the extra security over customizing UID/GIDs. Skipping the `chown` command in that case will make the...

That might indeed explain it! I've linked the issue to the PR so it will be closed when it is merged. If it still occurs after that we can reopen...

This is still an issue, see: https://github.com/openhab/openhab-addons/runs/7269653198

Still unstable, see: https://github.com/openhab/openhab-addons/actions/runs/3129621749/jobs/5078939913 ``` TEST org.openhab.binding.wemo.internal.handler.test.WemoHandlerOSGiTest#assertThatThingHandlesREFRESHCommandCorrectly()

I rebuild them using the same sources as nrjavaserial but with some different compiler flags. See this [nrjavaserial-builder](https://github.com/wborn/nrjavaserial-builder/) Docker container. I will no longer recompile the libraries, because all issues...

> the key functional difference is your use of the lockdev/liblockdev1 library That's right, the locking with liblockdev used by nrjavaserial was causing issues so I recompiled the libraries to...