chore: drop container_name from alloy and traffmonetizer

alloy/README.md

@@ -9,8 +9,7 @@ collectors. A second, tiny container proxies a read-only slice of the Docker
 API to it. The Alloy config is embedded inline via Compose `configs:`, so
 there is no `config.alloy` on disk.
 
-Both containers have fixed names,
+`dockerproxy` publishes
-`container_name: alloy` and `alloy-dockerproxy`, and `dockerproxy` publishes
 `127.0.0.1:2375` — Alloy runs with host networking, so it has no compose
 network to reach the proxy over.
 

alloy/compose.yml

@@ -1,7 +1,6 @@
 services:
   alloy:
     image: grafana/alloy:v1.16.1
-    container_name: alloy
     restart: unless-stopped
     hostname: ${ALLOY_HOSTNAME:?required}
     network_mode: host                        # node_exporter netdev/netstat sees real host interfaces (eth0…) not veth
@@ -38,7 +37,6 @@ services:
 
   dockerproxy:
     image: tecnativa/docker-socket-proxy:v0.5.0
-    container_name: alloy-dockerproxy
     restart: unless-stopped
     security_opt:
       - no-new-privileges:true

traffmonetizer/README.md

@@ -1,7 +1,7 @@
 # traffmonetizer
 
 [TraffMonetizer](https://traffmonetizer.com) bandwidth-sharing client, defined
-in `compose.yml` with `container_name: tm` and `restart: always`. It
+in `compose.yml` with `restart: always`. It
 only makes outbound connections, so there is no port to map a domain to.
 
 `restart: always` instead of `unless-stopped` is on purpose: the client should

traffmonetizer/compose.yml

@@ -1,7 +1,6 @@
 services:
   traffmonetizer:
     image: 'traffmonetizer/cli_v2:arm64v8'
-    container_name: tm
     restart: always
     command: 'start accept --token ${TOKEN}'
     environment: