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

why run error #1956

Open
aogg opened this issue Aug 24, 2023 · 6 comments
Open

why run error #1956

aogg opened this issue Aug 24, 2023 · 6 comments

Comments

@aogg
Copy link

aogg commented Aug 24, 2023

docker rm -f temp-node;\
docker run --network common-all -d --entrypoint /usr/bin/bash --name temp-node  \
-v /data/:/data \
node:18 -c "tail -f /etc/hosts"

root@5fe9c6cb883b:/tmp# npm -v
node[18]: ../src/node_platform.cc:68:std::unique_ptr<long unsigned int> node::WorkerThreadsTaskRunner::DelayedTaskScheduler::Start(): Assertion `(0) == (uv_thread_create(t.get(), start_thread, this))' failed.
 1: 0xb83f50 node::Abort() [node]
 2: 0xb83fce  [node]
 3: 0xbf14ee  [node]
 4: 0xbf15d1 node::NodePlatform::NodePlatform(int, v8::TracingController*, v8::PageAllocator*) [node]
 5: 0xb41ed3 node::InitializeOncePerProcess(std::vector<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::allocator<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > > const&, node::ProcessFlags::Flags) [node]
 6: 0xb4256b node::Start(int, char**) [node]
 7: 0x7e916c7f41ca  [/lib/x86_64-linux-gnu/libc.so.6]
 8: 0x7e916c7f4285 __libc_start_main [/lib/x86_64-linux-gnu/libc.so.6]
 9: 0xac1fee _start [node]
Aborted (core dumped)
root@5fe9c6cb883b:/tmp# 


@jkevinaxioned
Copy link

Even I am getting same error with node 18 version

@jkevinaxioned
Copy link

jkevinaxioned commented Aug 24, 2023

Update - Issue is now resolved for me. The error was due to use of old docker version v19 and updated to docker version v23.

@aogg Try to update your docker version, it should get resolved.

@aogg
Copy link
Author

aogg commented Aug 24, 2023

So there is something wrong with your image, not the need to upgrade the node version

@jkevinaxioned
Copy link

No nothing wrong with the image, just need to upgrade the docker version.

@aogg
Copy link
Author

aogg commented Aug 31, 2023

The current version of docker 20.10.7 is already very new, why do you need to upgrade to version 23 and why do you not support version 20?

And what I found the solution is that I need to turn on the system permissions-- privileged.
Add-- privileged will run, it doesn't make sense.

@yosifkit
Copy link
Contributor

yosifkit commented Sep 5, 2023

--privileged worked? then I'd guess that it is likely a seccomp denial similar to #1931, and #1932, and so docker-library/python#837 (comment) has some ideas for a temporary workaround (try --security-opt seccomp=unconfined), a longer workaround (try a different base OS, like -bullseye) and fix (update libseccomp and docker).

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

3 participants