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.

Sign up for GitHub

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

Jump to bottom

our distribution, identified as "bionic", is not currently supported #904

Closed
stackoverflow2 opened this issue Sep 18, 2019 · 9 comments
Closed

our distribution, identified as "bionic", is not currently supported #904

stackoverflow2 opened this issue Sep 18, 2019 · 9 comments

Comments

@stackoverflow2
Copy link

Your distribution, identified as "bionic", is not currently supported, please contact NodeSource at https://github.com/nodesource/distributions/issues if you think this is incorrect or would like your distribution to be considered for support
@wolfy1339
Copy link

No longer a problem, this has been fixed.

@stackoverflow2
Copy link
Author

@wolfy1339 okay.
Thank you.

@Bugazelle
Copy link

@wolfy1339

From my end, still not working. I am using the ubuntu:18.04 docker.
Would you please give us a clear step to make it working?

root@cd74e0327cff:~# curl -sL -k https://deb.nodesource.com/setup_10.x | bash -

## Installing the NodeSource Node.js 10.x repo...


## Populating apt-get cache...

+ apt-get update
Hit:1 http://archive.ubuntu.com/ubuntu bionic InRelease
Get:2 http://security.ubuntu.com/ubuntu bionic-security InRelease [88.7 kB]
Get:3 http://archive.ubuntu.com/ubuntu bionic-updates InRelease [88.7 kB]
Get:4 http://archive.ubuntu.com/ubuntu bionic-backports InRelease [74.6 kB]
Fetched 252 kB in 10s (26.2 kB/s)
Reading package lists... Done

## Confirming "bionic" is supported...

+ curl -sLf -o /dev/null 'https://deb.nodesource.com/node_10.x/dists/bionic/Release'

## Your distribution, identified as "bionic", is not currently supported, please contact NodeSource at https://github.com/nodesource/distributions/issues if you think this is incorrect or would like your distribution to be considered for support

root@cd74e0327cff:~#

@wolfy1339
Copy link

wolfy1339 commented Oct 29, 2019 via email

@Bugazelle
Copy link

Find the reason, because we are behind the proxy, and the ssl certificate issue, failed to run setup_10.x script.

Suggest:
Add -k in curl command

@igsu
Copy link
Contributor

igsu commented Dec 16, 2019

This issue has been fixed, bionic is currently supported.
Closing this now.

@igsu igsu closed this as completed Dec 16, 2019
@Demasso
Copy link

Demasso commented Jan 13, 2020 •
edited
Loading

no it's not.

sudo bash nodesource_setup.sh

Installing the NodeSource Node.js 10.x repo...

Populating apt-get cache...

Confirming "bionic" is supported...

Your distribution, identified as "bionic", is not currently supported, please contact NodeSource at https://github.com/nodesource/distributions/issues if you think this is incorrect or would like your distribution to be considered for support

@igsu igsu mentioned this issue Feb 10, 2020
Closed
@mhedden
Copy link

mhedden commented Mar 3, 2020

Confirming "bionic" is supported...

Your distribution, identified as "bionic", is not currently supported, please contact NodeSource at https://github.com/nodesource/distributions/issues if you think this is incorrect or would like your distribution to be considered for support

Hi @Demasso. I had this same problem and found the issue for me was because my corporate proxy does a man in the middle and supplies a self signed certificate that was causing the curl command in the script to fail which is why I got that message.

So I had to add the self signed corporate root certificate to ubuntu's ca-certificates. I also modified the bash script to add --cacert /path/to/selfsigned.crt to the 2 curl commands in the script (ln 281 & ln 303 at time of writing). Although those modifications may not have been necessary after adding the cert to the system but I did it just in case.

After that I was able to install node 13.9.0 without issue. Hopefully this is helpful to anyone who was seeing the same issue and is behind a corporate proxy that inspects and re-signs what is passed through it.

@igsu igsu mentioned this issue Mar 16, 2020
Closed
@igsu igsu mentioned this issue May 15, 2020
Closed
@donovanmuller
Copy link

I had the same issue with using a corporate proxy but in my case just exporting the https_proxy environment variable worked for me:

$ export http_proxy=http://xxx
$ export https_proxy=http://xxx
$ curl -sL https://deb.nodesource.com/setup_current.x | sudo -E bash -
...

This was referenced Dec 15, 2021
Closed
Closed
Closed
This was referenced Dec 27, 2021
Closed
Closed
Closed
This was referenced Jan 5, 2022
Closed
Closed
@JesusPaz JesusPaz mentioned this issue Mar 1, 2022
Closed
@JesusPaz JesusPaz mentioned this issue Mar 22, 2022
Closed
This was referenced May 2, 2022
Closed
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
7 participants
@donovanmuller @wolfy1339 @Demasso @mhedden @stackoverflow2 @igsu @Bugazelle