You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
.dockerignore excludes .git/, target/, *.log, data, dist, bin, docs, tools and *.md — but not .env.
docker/build.Dockerfile does COPY . ., and docs/docker.md instructs
operators to create .env from .env.example. So a machine that has been
set up to run the node and then builds a binary copies its own .env into
the build context.
It does not reach the shipped artifact: the export target is FROM scratch
and contains only the binary. But it lands in build layers and the local
image cache, and would be present in the build image if that image were ever
pushed.
Today .env holds ports, a network id and an external IP — nothing secret.
The problem is the convention: .env is where secrets accumulate, and the
file is being introduced to this repository for the first time by the same
change that leaves it out of the ignore list.
Activity