🐛Docker container fails to connect out; "no recent network activity" via quic or "i/o timeout" on http2

**Describe the bug**
I am running cloudflared via the docker container on a registered cloudflare account. Neither quic nor http2 is connecting -- but I need help understanding where the failure is to properly diagnose with the network techs.

**To Reproduce**
Steps to reproduce the behavior:
1. Copy cloudflared docker container from the website, paste into terminal with docker running
2. docker run cloudflare/cloudflared:latest tunnel --no-autoupdate run --token *redacted*

If it's an issue with Cloudflare Tunnel:
4. Tunnel ID : 79c75e2e-1881-4324-9548-a879f42bde8a
5. cloudflared config: docker run cloudflare/cloudflared:latest tunnel --no-autoupdate run --token

**Expected behavior**
I expect to be able to connect out, I tried DIG, and udp out to the ips above. I have attempted nc -vzu connections to the ports as well as digs, please see logs and errors section

**Logs and errors**

```
2023-06-28T15:08:44Z ERR Failed to create new quic connection error="failed to dial to edge with quic: timeout: no recent network activity" connIndex=0 event=0 ip=198.41.200.23 ```
or when defaulting to http2
```59Z ERR Serve tunnel error error="DialContext error: dial tcp 198.41.192.77:7844: i/o timeout" connIndex=0 event=0 ip=198.41.192.77`
```

when attempting to troubleshoot via https://developers.cloudflare.com/cloudflare-one/connections/connect-apps/install-and-setup/ports-and-ips/

```
nc -vzu 198.41.200.13 7844
Connection to 198.41.200.13 7844 port [udp/*] succeeded!
nc -vzu 198.41.200.23 7844
Connection to 198.41.200.23 7844 port [udp/*] succeeded!
```
```
dig A region1.v2.argotunnel.com

; <<>> DiG 9.16.1-Ubuntu <<>> A region1.v2.argotunnel.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 18181
;; flags: qr rd ra; QUERY: 1, ANSWER: 10, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;region1.v2.argotunnel.com. IN A

;; ANSWER SECTION:
region1.v2.argotunnel.com. 6703 IN A 198.41.192.27
region1.v2.argotunnel.com. 6703 IN A 198.41.192.167
region1.v2.argotunnel.com. 6703 IN A 198.41.192.67
region1.v2.argotunnel.com. 6703 IN A 198.41.192.107
region1.v2.argotunnel.com. 6703 IN A 198.41.192.7
region1.v2.argotunnel.com. 6703 IN A 198.41.192.77
region1.v2.argotunnel.com. 6703 IN A 198.41.192.57
region1.v2.argotunnel.com. 6703 IN A 198.41.192.47
region1.v2.argotunnel.com. 6703 IN A 198.41.192.227
region1.v2.argotunnel.com. 6703 IN A 198.41.192.37

;; Query time: 0 msec
;; SERVER: 127.0.0.53#53(127.0.0.53)
;; WHEN: Wed Jun 28 11:26:27 EDT 2023
;; MSG SIZE rcvd: 214
```

and
```
dig AAAA region1.v2.argotunnel.com

; <<>> DiG 9.16.1-Ubuntu <<>> AAAA region1.v2.argotunnel.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 31966
;; flags: qr rd ra; QUERY: 1, ANSWER: 10, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;region1.v2.argotunnel.com. IN AAAA

;; ANSWER SECTION:
region1.v2.argotunnel.com. 16879 IN AAAA 2606:4700:a0::6
region1.v2.argotunnel.com. 16879 IN AAAA 2606:4700:a0::9
region1.v2.argotunnel.com. 16879 IN AAAA 2606:4700:a0::1
region1.v2.argotunnel.com. 16879 IN AAAA 2606:4700:a0::5
region1.v2.argotunnel.com. 16879 IN AAAA 2606:4700:a0::4
region1.v2.argotunnel.com. 16879 IN AAAA 2606:4700:a0::8
region1.v2.argotunnel.com. 16879 IN AAAA 2606:4700:a0::2
region1.v2.argotunnel.com. 16879 IN AAAA 2606:4700:a0::7
region1.v2.argotunnel.com. 16879 IN AAAA 2606:4700:a0::10
region1.v2.argotunnel.com. 16879 IN AAAA 2606:4700:a0::3

;; Query time: 0 msec
;; SERVER: 127.0.0.53#53(127.0.0.53)
;; WHEN: Wed Jun 28 11:27:13 EDT 2023
;; MSG SIZE rcvd: 334
```

and
```
dig A region2.v2.argotunnel.com

; <<>> DiG 9.16.1-Ubuntu <<>> A region2.v2.argotunnel.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 494
;; flags: qr rd ra; QUERY: 1, ANSWER: 10, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;region2.v2.argotunnel.com. IN A

;; ANSWER SECTION:
region2.v2.argotunnel.com. 84937 IN A 198.41.200.43
region2.v2.argotunnel.com. 84937 IN A 198.41.200.23
region2.v2.argotunnel.com. 84937 IN A 198.41.200.13
region2.v2.argotunnel.com. 84937 IN A 198.41.200.73
region2.v2.argotunnel.com. 84937 IN A 198.41.200.233
region2.v2.argotunnel.com. 84937 IN A 198.41.200.53
region2.v2.argotunnel.com. 84937 IN A 198.41.200.33
region2.v2.argotunnel.com. 84937 IN A 198.41.200.193
region2.v2.argotunnel.com. 84937 IN A 198.41.200.113
region2.v2.argotunnel.com. 84937 IN A 198.41.200.63

;; Query time: 0 msec
;; SERVER: 127.0.0.53#53(127.0.0.53)
;; WHEN: Wed Jun 28 11:27:42 EDT 2023
;; MSG SIZE rcvd: 214
```

and
```
dig AAAA region2.v2.argotunnel.com

; <<>> DiG 9.16.1-Ubuntu <<>> AAAA region2.v2.argotunnel.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 350
;; flags: qr rd ra; QUERY: 1, ANSWER: 10, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;region2.v2.argotunnel.com. IN AAAA

;; ANSWER SECTION:
region2.v2.argotunnel.com. 84908 IN AAAA 2606:4700:a8::9
region2.v2.argotunnel.com. 84908 IN AAAA 2606:4700:a8::10
region2.v2.argotunnel.com. 84908 IN AAAA 2606:4700:a8::7
region2.v2.argotunnel.com. 84908 IN AAAA 2606:4700:a8::8
region2.v2.argotunnel.com. 84908 IN AAAA 2606:4700:a8::2
region2.v2.argotunnel.com. 84908 IN AAAA 2606:4700:a8::1
region2.v2.argotunnel.com. 84908 IN AAAA 2606:4700:a8::3
region2.v2.argotunnel.com. 84908 IN AAAA 2606:4700:a8::6
region2.v2.argotunnel.com. 84908 IN AAAA 2606:4700:a8::5
region2.v2.argotunnel.com. 84908 IN AAAA 2606:4700:a8::4

;; Query time: 0 msec
;; SERVER: 127.0.0.53#53(127.0.0.53)
;; WHEN: Wed Jun 28 11:28:11 EDT 2023
;; MSG SIZE rcvd: 334

**Environment and versions**
- OS: Ubuntu
- Architecture: Intel Arm docker run cloudflare/cloudflared --version
cloudflared version 2023.6.1 (built 2023-06-20-0923 UTC)
- Version: [e.g. 2022.02.0]
```
**Additional context**
I wonder if it's the docker container? Unfortunately, as this machine is managed, we can not run sudo for new code installs without a thorough and lengthy review.

Beginnen Sie mit dem Docker-Befehl, der cloudflared-Version und den QUIC- und HTTP/2-Timeout-Logs und vergleichen Sie dann die gemeldeten Tests mit der im Issue verlinkten Dokumentation zu Ports und IPs. Keine Quelldatei oder kein Test wird genannt, und das Issue definiert weder eine Codeänderung noch klare Akzeptanzkriterien; abgeschlossen wäre die Arbeit erst, wenn isoliert ist, ob der Fehler im Container oder im verwalteten Netzwerk liegt, und ein reproduzierbarer Fix dokumentiert ist.

Vom Indexierungsmodell aus dem Issue-Text verfasst.