Closed craftyguy closed 2 years ago
This would be due to the call to getaddrinfo
in get_hostname_fqdn
, which is used to determine the right side of Message-IDs (xxxx@yyyy) of any messages we create. I think there might be privacy implications of revealing the hostname or FQDN anyway, so we could just take the domain name from the From address.
EDIT: that's on the message-id-domain
branch now
The "posix_spawn failed" error is strange though.
ah yeah seems like the posix_spawn failed
is unrelated, I no longer get timeouts on that message-id-domain
branch. So I think the original issue I reported is resolved, thanks!
I totally don't expect you to support this way of running bower (using namespaces to constrain it), so feel free to ignore this... but if you're curious...
here's the strace (using the branch above):
I'm running it like this, with bubblewrap:
$ bwrap --ro-bind /usr/bin /usr/bin --ro-bind /lib /lib --ro-bind /usr/lib /usr/lib --ro-bind /proc/self /proc/self --ro-bind /run/dbus /run/dbus --ro-bind /etc/localtime /etc/localtime --ro-bind /usr/share/zoneinfo /usr/share/zoneinfo --tmpfs /usr/lib/gcc --setenv XDG_RUNTIME_DIR /var/run/user/1000 --setenv HOME $HOME --dir /var/run/user/1000 --dev /dev --ro-bind $HOME/.notmuch-config $HOME/.notmuch-config --ro-bind $HOME/Mail $HOME/Mail --ro-bind $HOME/.config/bower $HOME/.config/bower /usr/bin/bower
I've merged the branch to master.
thank you!
I'm trying to run bower in a new network namespace (on Linux) that does not have any network interfaces or connectivity at all (so, no
lo
, etc), and bower seems to have a hard requirement on that:The only reference to any network connection requirement is a brief mention of bower using ssh to access a remote notmuch. Is there a way to disable this and run bower completely "offline" ?