Skip to content

Conversation

stigkj
Copy link
Contributor

@stigkj stigkj commented Oct 19, 2016

If you have this environment variable:

no_proxy=*.local, 169.254/16

it is very hard to get the quoting correct. It is easier to just write
the correct entries to the seluser's .bash_aliases file, which will be
included by .bashrc when running xvfb-run as the seluser.

If you have this env. var:

no_proxy=*.local, 169.254/16

it is very hard to get the quoting correct. It is easier to just write
the correct entries to the seluser's .bash_aliases file, which will be
included by .bashrc when running xvfb-run as the seluser.
@ddavison
Copy link
Member

this is a step in the right direction. I still had to run my node-chrome-debug using -e no_proxy="" -e HUB_ENV_no_proxy="", but that's just because of the Docker issue on OSX

@tazle
Copy link

tazle commented Nov 3, 2016

This same problem exists in 2.53.1 as reported in #327

@a-k-g
Copy link
Contributor

a-k-g commented Nov 8, 2016

Should solve #227 as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants