Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

https://github.com/facebook/wangle/blob/master/wangle/bootstrap/BootstrapTest.cpp#L354 #76

Closed
banro21 opened this issue Nov 1, 2016 · 2 comments

Comments

@banro21
Copy link

banro21 commented Nov 1, 2016

May be I am ignorant, but when i run ctest it fails to create a socket. However when i change it 127.0.0.1, it works

ubuntu 14.0.4

@OliverMD
Copy link

OliverMD commented Nov 1, 2016

I presume you are referring to

  SocketAddress localhost("::1", 0);

"::1" is the ipv6 loopback address. From my (limited) understanding this means that you don't have an ipv6 address bound to your loopback interface or ipv6 isn't enabled on your box.

You can check by running ifconfig -a and seeing what you have for the lo interface. For example on my machine I have ipv6 enabled and so I see the following for lo:

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:1899 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1899 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1 
          RX bytes:176876 (176.8 KB)  TX bytes:176876 (176.8 KB)

I suspect you will not see inet6 addr: ::1/128 Scope:Host.

You can find out more about ipv6 on the ubuntu wiki article IPv6.

@banro21
Copy link
Author

banro21 commented Nov 1, 2016

@OliverMD Thanks. I will try to with changing my VM configs.

@banro21 banro21 closed this as completed Nov 1, 2016
facebook-github-bot pushed a commit that referenced this issue Apr 11, 2019
Summary:
Needs to be enabled by option PYTHON_VENV in the config.

shell_builder.py sets up the venv and uses it once; calling activate

For docker we set ENV; resulting in the virtual environment being present
when the resulting container is run as well as at build time. This is also cleaner
and easier to follow than re-asserting on each RUN step.

For Lego builder we need to source activate on each command as environment
will not persist between commands.

While man on the posts say it makes no sense to use virtualenv within docker
container, this method simplifies the process considerably as we can rely on the
name pip being valid and we don't need to either ensure we are root or pass the
--user flag to pip and setuptools.

Pull Request resolved: facebookarchive/LogDevice#76

Reviewed By: wez

Differential Revision: D14875633

Pulled By: calebmarchent

fbshipit-source-id: aabbcdd509d2a59fa36f8004032a052f014ce1ba
facebook-github-bot pushed a commit that referenced this issue Mar 14, 2022
Summary:
X-link: facebookincubator/fizz#76

X-link: facebook/proxygen#402

X-link: facebook/folly#1735

X-link: facebookarchive/bistro#60

X-link: facebook/watchman#1012

X-link: facebook/fbthrift#487

X-link: facebook/fboss#114

X-link: facebook/fb303#27

When using getdeps inside of a container, Python's urllib isn't able to download from dewey lfs (see this post for details https://fb.workplace.com/groups/systemd.and.friends/permalink/2747692278870647/).

This allows for getdeps to use `libcurl` to fetch dependencies, which allows for a getdeps build to work inside the container environment.

Reviewed By: mackorone

Differential Revision: D34696330

fbshipit-source-id: 06cae87eef40dfa3cecacacee49234b6737d546f
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

No branches or pull requests

2 participants