v0.2.52

Private registries and compose builds now work under systemd. The systemd unit's hardening left docker login without a writable config directory and /tmp read-only, so pulls from private registries were unauthorized and docker compose build failed with mkdir /root/.docker: read-only file system. The unit now sets RuntimeDirectory=hawser and points DOCKER_CONFIG and TMPDIR at /run/hawser (tmpfs: logins never reach the disk), and compose now honours DOCKER_CONFIG. A failed registry login is logged as a warning.

systemd users: re-run the installer to get the new unit; swapping only the binary keeps the old unit and the old behaviour:

curl -fsSL -o install.sh https://raw.githubusercontent.com/Finsys/hawser/main/scripts/install.sh
bash install.sh

${TMPDIR} and ${DOCKER_CONFIG} in a compose file now resolve to /run/hawser

Changelog

• 81e529a docker login and compose share one writable config dir: DOCKER_CONFIG and TMPDIR reach compose, systemd units point them at /run/hawser (tmpfs); a failed login is a warning
• dcba146 gofmt deniedEnvKeys alignment
• 0bc320d test that compose gets DOCKER_CONFIG and TMPDIR from Execute; README: ${TMPDIR} and ${DOCKER_CONFIG} in a compose file resolve to /run/hawser