-
Notifications
You must be signed in to change notification settings - Fork 529
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
Content of /proc/net/tcp not what it is supposed to be #143
Comments
I'll do some investigation. It is beyond my initial knowledge of the musl libc TCP implementation. What is this actually affecting? |
I guess it's affecting every tools that use this file to gather system information such as |
Just FYI, it works as expected when spawning a http server with the go |
I just hit this "bug" as well. You need to do "nc -l -p 9999" |
I've noticed something weird I couldn't reproduce on other docker images such as
ubuntu
or on a "real" distribution (i.e: not running in a container engine).When I launch the command:
nc -l 9999
, I expect to see the in/proc/net/tcp
something like this:where the
00000000:270F
part corresponds to<local_addr>:<local_port>
. In this sample, I see0.0.0.0:9999
(once converted to decimal). However on alpine docker I see random number for the port part instead of the 9999 I expect.Here is a screenshot of my session:
The text was updated successfully, but these errors were encountered: