Closed jack1902 closed 4 years ago
to: cc: @subspacecommunity/subspace-maintainers related to: resolves: #90 #97
Bug reports were raised and this is how i can fix it. There MIGHT be a better solution than this in terms of using KEY=VALUE as part of the below. But i personally feely like this approach is better as ALL environment variables are only relevant to subspace https://github.com/subspacecommunity/subspace/blob/15ff6dbc430d3f28f61b44d237604783a5f4865d/bin/my_init#L30
KEY=VALUE
subspace
/etc/envvars
env > /data/wireguard/environment
entrypoint.sh
docker-compose
to: cc: @subspacecommunity/subspace-maintainers related to: resolves: #90 #97
Background
Bug reports were raised and this is how i can fix it. There MIGHT be a better solution than this in terms of using
KEY=VALUEas part of the below. But i personally feely like this approach is better as ALL environment variables are only relevant tosubspacehttps://github.com/subspacecommunity/subspace/blob/15ff6dbc430d3f28f61b44d237604783a5f4865d/bin/my_init#L30Changes
/etc/envvarsfile before callingsubspaceTesting
env > /data/wireguard/environmenttoentrypoint.shline 179 and observed the expected envvars as passed in fromdocker-compose