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

node package needed #106

Closed
eyberg opened this issue Jan 2, 2019 · 6 comments
Closed

node package needed #106

eyberg opened this issue Jan 2, 2019 · 6 comments
Labels

Comments

@eyberg
Copy link
Contributor

eyberg commented Jan 2, 2019

@mkhon reported having hello world working here (after merging a few nanos branches) - should go ahead and get an initial build for this

@eyberg eyberg added the packages label Jan 2, 2019
@eyberg
Copy link
Contributor Author

eyberg commented Jan 4, 2019

document that we currently only support 11.5.0 for now

nanovms/nanos#241

@eyberg eyberg added the docs label Jan 4, 2019
@eyberg
Copy link
Contributor Author

eyberg commented Jan 14, 2019

I think we need to add libnss && certs to the node pkg

➜  tn  ops load node_v11.15.0 -a bob.js
Downloading.. /Users/eyberg/go/bin/.packages/node_v11.15.0.tar.gz
 15.62 MiB / 15.62 MiB [=======================================================] 100.00% 7.30 MiB/s 2s
Extracting /Users/eyberg/go/bin/.packages/node_v11.15.0.tar.gz...
/var/folders/7q/rszjwjd14tl2cndscyy1q5jh0000gn/T/resolv=>/etc/resolv.conf
/var/folders/7q/rszjwjd14tl2cndscyy1q5jh0000gn/T/hostname=>/proc/sys/kernel/hostname
bob.js=>bob.js
.staging/node_v11.15.0/node=>node_v11.15.0/node
.staging/node_v11.15.0/package.manifest=>node_v11.15.0/package.manifest
.staging/node_v11.15.0/sysroot/lib/x86_64-linux-gnu/libc.so.6=>lib/x86_64-linux-gnu/libc.so.6
.staging/node_v11.15.0/sysroot/lib/x86_64-linux-gnu/libdl.so.2=>lib/x86_64-linux-gnu/libdl.so.2
.staging/node_v11.15.0/sysroot/lib/x86_64-linux-gnu/libgcc_s.so.1=>lib/x86_64-linux-gnu/libgcc_s.so.1
.staging/node_v11.15.0/sysroot/lib/x86_64-linux-gnu/libm.so.6=>lib/x86_64-linux-gnu/libm.so.6
.staging/node_v11.15.0/sysroot/lib/x86_64-linux-gnu/libpthread.so.0=>lib/x86_64-linux-gnu/libpthread.so.0
.staging/node_v11.15.0/sysroot/lib/x86_64-linux-gnu/librt.so.1=>lib/x86_64-linux-gnu/librt.so.1
.staging/node_v11.15.0/sysroot/lib64/ld-linux-x86-64.so.2=>lib64/ld-linux-x86-64.so.2
.staging/node_v11.15.0/sysroot/usr/lib/x86_64-linux-gnu/libstdc++.so.6=>usr/lib/x86_64-linux-gnu/libstdc++.so.6
booting image ...
assigned: 10.0.2.15
epoll_wait error: requested fd 16 (eventmask 19) missing check
epoll_wait error: requested fd 18 (eventmask 19) missing check
dns.js:113
    throw new ERR_INVALID_OPT_VALUE('family', family);
    ^

TypeError [ERR_INVALID_OPT_VALUE]: The value "4294967295" is invalid for option "family"
    at lookup (dns.js:113:11)
    at net.js:979:5
    at defaultTriggerAsyncIdScope (internal/async_hooks.js:294:19)
    at lookupAndConnect (net.js:978:3)
    at TLSSocket.Socket.connect (net.js:913:5)
    at Object.connect (_tls_wrap.js:1248:12)
    at Agent.createConnection (https.js:119:22)
    at Agent.createSocket (_http_agent.js:227:26)
    at Agent.addRequest (_http_agent.js:185:10)
    at new ClientRequest (_http_client.js:261:16)
epoll_wait error: requested fd 11 (eventmask 19) missing check
epoll_wait error: requested fd 13 (eventmask 19) missing check
exit_groupexit status 1
➜  node_v11.15.0  tree
.
├── node
├── package.manifest
└── sysroot
    ├── lib
    │   └── x86_64-linux-gnu
    │       ├── libc.so.6
    │       ├── libdl.so.2
    │       ├── libgcc_s.so.1
    │       ├── libm.so.6
    │       ├── libpthread.so.0
    │       └── librt.so.1
    ├── lib64
    │   └── ld-linux-x86-64.so.2
    └── usr
        └── lib
            └── x86_64-linux-gnu
                └── libstdc++.so.6

7 directories, 10 files

@cbarraford
Copy link
Contributor

@eyberg are you sure you want to document that we only support 11.5.0? Its presumed by the results of ops list, yes?

@eyberg
Copy link
Contributor Author

eyberg commented Jan 15, 2019

kind of - someone could download a newer/older version && build a similar package and find it breaking - afaik it's not fixed yet - until it is i think it's worth having in the docs - as a general rule of thumb though - we're going to run into this sort of issue quite a lot w/random software for a while - i suppose if it's noted in an issue for now that's good enough for 'documentation' but agreed that any package we build implies that we've blessed it to a certain degree - this can be closed once libnss && certs are pkg'd in

@mkhon
Copy link
Contributor

mkhon commented Jan 15, 2019

I think older versions(including 10.x) are supported now

@cbarraford
Copy link
Contributor

@eyberg do you think its worthwhile to have a page per package with notes etc etc? Or do you want to just open an issue like you suggested?

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

No branches or pull requests

4 participants