Update src/Testcontainers/TarArchiveDefaults.cs

Author: HofmeisterAn

src/Testcontainers/TarArchiveDefaults.cs

@@ -4,18 +4,18 @@ internal static class TarArchiveDefaults
   {
     // A block factor of 1 keeps the record size equal to the block size (512 B),
     // so SharpZipLib writes no extra zero padding beyond the two standard EOF
-    // blocks. The default factor of 20 produces ~8 KB of trailing zeros, which
-    // can trigger a race in Podman's archive handler. The tar subprocess exits
-    // after the EOF blocks while the HTTP sender is still flushing the padding,
-    // resulting in an EPIPE (HTTP 500 "broken pipe"). See:
-    // https://github.com/testcontainers/testcontainers-dotnet/issues/1683.
+    // blocks. The default factor of 20 produces up to 9 KiB of trailing zero
+    // padding, which can trigger a race in Podman's archive handler. The tar
+    // subprocess exits after the EOF blocks while the HTTP sender is still
+    // flushing the padding, resulting in an EPIPE (HTTP 500 "broken pipe").
+    // See: https://github.com/testcontainers/testcontainers-dotnet/issues/1683.
     //
     // The race only affects PUT /containers/{id}/archive (resource mappings via
     // a MemoryStream). Buildah's copierHandlerPut returned immediately after
     // tar.Reader reached io.EOF without draining the pipe. POST /build is immune
     // because containers/storage's chrootarchive.Untar always drains stdin after
-    // extraction. The server-side fix landed in buildah. See:
-    // https://github.com/podman-container-tools/buildah/pull/6678.
+    // extraction. The server-side fix landed in buildah.
+    // See: https://github.com/podman-container-tools/buildah/pull/6678.
     // Keeping the block factor at 1 stays correct for older Podman versions.
     //
     // Do NOT use this for the Dockerfile build context, which is written to a