Jasper Ben Orschulko

> Hello. You forgot to remove the warning too. Can confirm this behavior. The notifications are gone, however the warning within the client is still there.

:wave: Has there been some progress here? :slightly_smiling_face:

At least for your scenario Nr.3 the issue seems to be the this: ``` securityContext: capabilities: drop: [ALL] ``` the following configuration works for me: ``` hostNetwork: true ports: web:...

Seems I missed the unprivileged part ;) I agree with you, running as root should be avoided, however when running as non root, the permission denied error still persists. Yes,...

@madebr from https://github.com/mattgodbolt/seasocks/pull/144#issuecomment-670523298 I take it, that `conan create .` should default to a static package? This would also be the default behavior in the previous release. Conan also reports...

> The change to the default shared seems wrong; also defining SEASOCKS_SHARED appears counter to the idea of using BUILD_SHARED_LIBS (which is working now!) > > But! I'll add the...

Would be appreciated. We currently use "plain" CMake but as the person who recently had the glorious task of ensuring license compliance in my companies product, I feel somewhat obligated...

We are running into the same issue and can confirm that this is an issue with WAL-E configuration. Without configuring WAL-E everything works as expected. But as soon as we...

> Even with `master` or the latest release (`1.3.6`), setting the AP to `0:0`, a simple `chown -R root:root /path` as uid `0`, still gives: > > ``` > chown:...

> > When setting `uid` and `gid` to `0` (root) and then creating a new file within the mountpath as any other user than root (this will chown the file...