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
postgres calls the archive/restore command with a very limited env, notably, $PATH and $HOME are missing. As such, the home dir detection of github.com/mitchellh/go-homedir fails, as it can't find getent.
Looking for the code, there are two other places where the homedir is used - internal/crypto.go and internal/config.go. Both use os/user.Current. Is there a reason why cmd/root.go uses the other way? Nonetheless, a workaround right now is to
use HOME=/path/to/dir /usr/bin/wal-g.
The text was updated successfully, but these errors were encountered:
Hi! Sorry for so long delay...
Yes, this go-home thing certainly is a problem: usages should be unified. And if we really need go-homedir, it should be in gopkg.toml?
postgres calls the archive/restore command with a very limited env, notably,
$PATH
and$HOME
are missing. As such, the home dir detection ofgithub.com/mitchellh/go-homedir
fails, as it can't findgetent
.There is a fix for that (mitchellh/go-homedir#18) but that's on in the v1.1.0 release.
Looking for the code, there are two other places where the homedir is used -
internal/crypto.go
andinternal/config.go
. Both useos/user.Current
. Is there a reason whycmd/root.go
uses the other way? Nonetheless, a workaround right now is touse
HOME=/path/to/dir /usr/bin/wal-g
.The text was updated successfully, but these errors were encountered: