Unable to clone a repository with the node docker image

[AymarN]

Environment

• Platform: CentOS
• Docker Version: Docker version 17.03.1-ce, build c6d412e
• Node.js Version: v22.2.0
• Image Tag: latest

Expected Behavior

I shall be able to clone a repository on Github through https or ssh on the node docker image

Current Behavior

While cloning a repository from Github https or ssh, on the node image, an error is showing on

ssh : The authenticity of host can't be established

https:// fatal: unable to access 'https://github.com/json-schema-org/website.git/': getaddrinfo() thread failed to start

Possible Solution

provide key details regarding the dockerfile to help build another image.

Steps to Reproduce

1. Pull the docker image on Docker.com
2. Run it
3. clone a github repository through ssh or https
4. In both cases, an error is showing on.

Additional Information

[LaurentGoderre]

This might have to do with your network. I can't reproduce locally.

[AymarN]

Thank unto you for your answer. I am able to clone any repos on GitHub on my local computer. However , the errors that I have is on the node image.
Give me enough time to keep on investigating.

[AymarN]

Good Morning All,
I think it is not a network issue. I cloned the repository on my local computer. There is no issue regarding cloning. The issue is regarding node limitation on my local computer. However on the node image which I pulled from docker I can't clone the repository through ssh.Whether I may have the docker file I could generate another image and try.

[LaurentGoderre]

Docker 17 is very old. I would recommend updating that first to see if that helps

[AymarN]

Thank you for your answer.
Do you have a link to a recent docker image that I may pull or an alternative ?

[LaurentGoderre]

It's not the image but the docker engine itself

[AymarN]

Thank you.
I am using Docker version 26.1.4, build 5650f9b.
Which version shall I use to get an appropriate version of node version ?
Also, when the node image is pulled. Is NPM systematically set up ?

[yosifkit]

"thread failed to start" sounds like a libseccomp issue. Try running with --security-opt seccomp=unconfined and see if that makes the problems go away. If it does, then you'll need to make sure that docker, libseccomp and other dependent packages
(like containerd and runc) are up to date, but it could be that your Linux distro (CentOS) doesn't have a new enough version of libseccomp.

See also docker-library/official-images#16829.

[AymarN]

Thank you. Let me get back to you soon.

[nschonni]

Closing as these seems like a networking on Docker issue, and not related to this specific image. There are no changes that would happen in this repo that would address your local problem

[AymarN]

"thread failed to start" sounds like a libseccomp issue. Try running with --security-opt seccomp=unconfined and see if that makes the problems go away. If it does, then you'll need to make sure that docker, libseccomp and other dependent packages (like containerd and runc) are up to date, but it could be that your Linux distro (CentOS) doesn't have a new enough version of libseccomp.

See also docker-library/official-images#16829.

Thank you for your feedback. I've switched temporary to a Windows computer. I do not encounter network issue . Therefore, I may perform the test again on CentOs with an updated version of Docker.

I was using CentOs Linux 7 that is no longer maintained. I may upgrade a computer to CentOs Linux 8 or CentOs Linux 9 to check the latest Docker version available.

Docker version 27.0.3, build 7d4bcd8
Windows 10 Pro