- Shipped
- 18 ஜூலை, 2026 அன்று 7:25 PM UTC
- Author
- kamo
- Commit
- af819cf
kamo-internal has not deployed since 2026-07-16: every build died in npm ci with ENOTFOUND k1m1 while fetching the private @kamo/* packages, which package-lock.json resolves as http://k1m1:3000/... . "k1m1" is in the HOST's /etc/hosts (192.168.4.22) but there is no DNS record for it, so it does not resolve inside the build container. Verified directly on the node: a default- network container fails to resolve k1m1, while 192.168.4.22:3000 is reachable from one. Maps the name to that address for the build. Fixing it here rather than in .npmrc or the lockfile keeps local development — where k1m1 does resolve — working unchanged.