🐛Cannot fix Docker cloudflared container logs error "Failed to sufficiently increase send buffer size"

**Describe the bug**
Running **cloudflared** via Docker produces an error in the logs but still runs fine:
`Failed to sufficiently increase send buffer size (was: 208 kiB, wanted: 2048 kiB, got: 416 kiB). See https://github.com/quic-go/quic-go/wiki/UDP-Buffer-Sizes for details`

**How To Reproduce**
Steps to reproduce the behavior:
1. Install the Docker **cloudflared** image via a simple compose file
2. Launch the container
3. See error in the logs
4. cloudflared config (compose.yml)

```
version: "3.9"
services:
tunnel:
container_name: cloudflared
image: cloudflare/cloudflared:latest
restart: always
command: tunnel run
environment:
- TUNNEL_TOKEN=
```

**Expected behavior**
This error should not be displayed, at least not when using Docker **cloudflared** image, I think.

**Environment and versions**
- OS: OpenMediaVault 6.9.13-1 (Debian 11)
- Architecture: Intel x64
- Version: Latest **cloudflared** image (the issue has been there for sometime)

**Logs and errors**
Despite the fact that the Docker image/container works fine, I get this error in logs:
`Failed to sufficiently increase send buffer size (was: 208 kiB, wanted: 2048 kiB, got: 416 kiB). See https://github.com/quic-go/quic-go/wiki/UDP-Buffer-Sizes for details.`

**Additional context**
I have read carefully the Wiki in question and have increased these buffers on the actual OMV (Debian) server side by adding the right parameters in `/etc/sysctl.conf` that survive reboot and report the correct intended/set values. However this doesn't seem to pass to Docker and I get still the error above.
```
net.core.rmem_max=26214400
net.core.rmem_default=26214400
```
Moreover, I tried adding **sysctls** to my compose file, so that these are set on Docker-level, but the specific net.core.rmem parameters are not accepted, an error is reproduced.

Raised this in [the OMV forum](https://forum.openmediavault.org/index.php?thread/51375-docker-cloudflare-tunnel-container-logs-error-failed-to-sufficiently-increase-se/) with no results or fix possible on the server-level.
Thank you.