youcef zr 85211afd41 fix: preserve HOME in compose deploy so --with-registry-auth can read docker config (#4485) ...

The compose/stack deploy command runs under `env -i PATH="$PATH"`, which
clears the environment except for PATH. That strips HOME, so when the
generated command is `docker stack deploy --prune --with-registry-auth`
the docker CLI cannot resolve `~/.docker/config.json` (e.g.
`/root/.docker/config.json`) and ships no registry credentials to the
swarm. Private-registry images then fail to pull on the nodes:

  image registry.example.com/... could not be accessed on a registry to
  record its digest. Each node will access ... independently

while the deploy still logs "Docker Compose Deployed: ✅".

Keep PATH isolation but preserve HOME so docker can read its config for
both `stack deploy --with-registry-auth` and `compose up -d --build`.

Add a regression test asserting the generated command preserves
`HOME="$HOME"` for both stack and docker-compose deploys.

Fixes #4401

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

2026-05-30 01:42:49 -06:00

..

api

fix: update import statements to include file extensions for consistency

2026-03-03 15:35:37 -06:00

dokploy

fix: preserve HOME in compose deploy so --with-registry-auth can read docker config (#4485)

2026-05-30 01:42:49 -06:00

monitoring

fix: enhance container metrics query to support wildcard matching for container names

2026-03-08 16:16:45 -06:00

schedules

[autofix.ci] apply automated fixes

2026-04-12 20:00:08 +00:00