Zeitpunkt Nutzer Delta Tröts TNR Titel Version maxTL Sa 06.07.2024 00:00:07 61.917 -2 3.523.632 56,9 Fosstodon 4.2.10 500 Fr 05.07.2024 00:00:27 61.919 0 3.520.710 56,9 Fosstodon 4.2.10 500 Do 04.07.2024 00:00:52 61.919 +2 3.517.337 56,8 Fosstodon 4.2.9 500 Mi 03.07.2024 00:00:12 61.917 +2 3.513.906 56,8 Fosstodon 4.2.9 500 Di 02.07.2024 00:01:44 61.915 -2 3.510.479 56,7 Fosstodon 4.2.9 500 Mo 01.07.2024 00:00:33 61.917 0 3.507.420 56,6 Fosstodon 4.2.9 500 So 30.06.2024 00:00:34 61.917 +2 3.504.671 56,6 Fosstodon 4.2.9 500 Sa 29.06.2024 00:01:13 61.915 +2 3.501.982 56,6 Fosstodon 4.2.9 500 Fr 28.06.2024 00:01:07 61.913 +3 3.498.459 56,5 Fosstodon 4.2.9 500 Do 27.06.2024 00:00:32 61.910 0 3.495.444 56,5 Fosstodon 4.2.9 500
Joongi Kim (@achimnol) · 11/2022 · Tröts: 9 · Folger: 16
Sa 06.07.2024 10:03
The race happens between the host-side port availability and the Docker's control on the port proxy processes. Docker performs acquire/release of the TCP ports safely "on its own". It is good if we only rely on the Docker's own port allocation. The problem occurs when we want to monitor the port availability from the host-side, separately to the Docker daemon, and reuse the ports in a short period of time by different containers.
[Öffentlich] Antw.: 0 Wtrl.: 0 Fav.: 0