SeaweedFS: S3 gateway on the compose network only

PocketBase reaches the gateway over the compose network (or inside the
AIO container), so publishing 8333 on the host only made a second
SeaweedFS stack fail with "port is already allocated". Drop the binding
and SEAWEED_S3_BIND/SEAWEED_S3_PORT.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Docker/docker-compose.prod.seaweedfs.split.yml

@@ -30,7 +30,7 @@ name: drivervault
 # filename overlap). So the two files are interchangeable on the same SEAWEED_DATA,
 # with no migration either way. A *second* volume server would need its own.
 #
-# Only the S3 gateway and the admin UI publish a host port. Master, volume and
+# Only the admin UI publishes a host port. The S3 gateway, master, volume and
 # filer are reachable over the compose network, through the admin UI, or with
 # `docker compose exec` — the volume server in particular serves file content by
 # id with no authentication at all, so it has no business on a public interface.
@@ -187,11 +187,7 @@ services:
       # Never serve before an identity exists — see seaweedfs-init above.
       seaweedfs-init:
         condition: service_completed_successfully
-    ports:
-      # Loopback only: the stack reaches the gateway over the compose network,
-      # so this is here for `aws s3 ls --endpoint-url http://127.0.0.1:8333` and
-      # nothing else. Set SEAWEED_S3_BIND=0.0.0.0 to expose it, and mean it.
-      - "${SEAWEED_S3_BIND:-127.0.0.1}:${SEAWEED_S3_PORT:-8333}:8333"
+    # No published port: the stack reaches the gateway over the compose network.
     healthcheck:
       test: ["CMD-SHELL", "wget -qO- http://127.0.0.1:8333/healthz || exit 1"]
       interval: 10s