Open dragon-dxw opened 1 week ago
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.
Correct, s6 sandboxes the container environment and by bypassing its init process with your own CMD you also bypass that environment.
This feels extremely X/Y so I would suggest explaining what you're actually trying to achieve rather than just providing random errors and expecting us to guess.
Is there an existing issue for this?
Current Behavior
With the following Dockerfile:
environment variables set via docker compose
neither the environment variables set via
.env
nor in docker compose appear.Expected Behavior
Swapping the libreoffice image for
debian
, the environment variables appear.Steps To Reproduce
(see current/expected behaviour)
Environment
CPU architecture
arm64
Docker creation
Container logs