On a Ubuntu 20.04 server - I've also tried removing and reinstalling curl as per This SO answer.
This
is also open.. So no idea how to install Node v14 LTS under nvm now..
The readme on the github for NVM says to use the provided install script for Linux installs. This can be achieved with curl or wget:
curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.38.0/install.sh | bash
wget -qO- https://raw.githubusercontent.com/nvm-sh/nvm/v0.38.0/install.sh | bash
I recommend that you click the link and read, as their is quite a bit of related info there.
I was interested and just tested it out in a clean docker container (ubuntu:20.04) (as I dont use node that often), and it looked pretty straight forward:
apt-get update -y
apt-get install -y curl
curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.38.0/install.sh | bash
source ~/.bashrc
nvm version
# none
nvm install --lts --default
nvm version
# v14.17.0
If it not that, then I would also assume, that the issue is related to your general environment, like network inspection, proxy access or else.
As it is visible from the logs, the checksum process keeps failing in a repeated manner. And there have been issues highlighting that some ISO images can show issue with hashing process due to Windows 10 components. , which implicitly effects the checksum process under a guest environment on VirtualBox.
You can complete the steps provided by VirtualBox team there to resolve this issue, as pointed out on Virtual Box's forum:
it's Hyper-V that is causing the checksum problem you posted about, not the version of Virtualbox.
Related
I'm trying to install nvm / node on an AMZ Linux 2 EC2 Instance using the following userData script:
#!/bin/bash
curl https://raw.githubusercontent.com/creationix/nvm/v0.39.1/install.sh | bash
. ~/.nvm/nvm.sh
nvm install 16.17.0
nvm use 16.17.0
However, when I SSH into the Instance, neither nvm nor node are installed. If I run the commands manually while SSH'd into the Instance, they work fine.
Anyone have any thoughts on why the installs don't work in the userData script? Thanks for any thoughts!
Although I still haven't figure out why the userData Script above doesn't work (it used to, so I'm not sure what changed), I was able to install Node using the following as userData, so I thought I'd share.
#!/usr/bin/env bash
yum update -y
curl -sL https://rpm.nodesource.com/setup_10.x | bash -
yum install -y nodejs git
I'd still be interested to know why the first script no longer works, if anyone has any idea.
Cheers!
Rob
Description: Ansible yum module doesn't install through control host, but local yum install works perfectly? What could cause such issue? I appreciate any response. Thank you guys. I worked on this 8 hours, I have researched various of things, and tried very different approaches. No success.
Node: Centos7 (newly installed), Control-Node: Ubuntu-LTS18.
Command:
ansible ansitest2 -i ../inv -b -m yum -a "name=epel-release state=present"
it can be any package though.
This fails, however at the bottom I can see that it found the package and tried to install it. ()
If I go to host itself and try to install it, it is successful. :
yum install epel-release -y
After spending almost 2 days on this, finally found answer, /etc/resolve.conf file needed to be updated with option rotate timeout:1,
So, if you have such issue, it is mainly about resolve.conf
man resolve.conf will give very good description.
I am using the following curl command to install poetry
curl -sSL https://raw.githubusercontent.com/sdispater/poetry/master/get-poetry.py | python
but poetry is getting stuck as shown in the image. Any help?
It could be related to the underlying use of pip and the keyring, it happened to me too with Poetry and found that was the underlying cause (see https://github.com/pypa/pip/issues/7883)
My temporary workaround is to disable the keyring by setting an env var.
export PYTHON_KEYRING_BACKEND=keyring.backends.null.Keyring
curl -sSL https://raw.githubusercontent.com/sdispater/poetry/master/get-poetry.py | python
My problem was that I had my machine set to check an Artifactory server that requires VPN access. I wasn't on the VPN so it was stuck trying to get to it.
This happened to me too, my issue was that some dependencies got stuck, so when I ran the installation with -vvv it got stuck on
<internal artifactory>: Downloading wheel: black-22.3.0-py3-none-any.whl
and running
poetry cache clean --all <internal artifactory>
helped.
The installation after wiping cache took long, but actually finished.
mkcert doesn't seem to be installed (or maybe not in the right path) on Ubuntu
ddev version
DDEV-Local version v1.8.0
commit v1.8.0
db drud/ddev-dbserver:v1.8.0-10.2
dba drud/phpmyadmin:v1.8.0
ddev-ssh-agent drud/ddev-ssh-agent:v1.8.0
docker 18.09.5
docker-compose 1.21.2
domain ddev.local
os linux
router drud/ddev-router:v1.8.0
web drud/ddev-webserver:v1.8.0
On Ubuntu 18
mkcert -install
zsh: command not found: mkcert
If you use( a package manager homebrew on Linux or macOS, or use the ddev Windows installer, or use Chocolatey on WIndows) then mkcert gets installed for you. In all other cases you have to install it yourself, see https://github.com/FiloSottile/mkcert
Note that mkcert is optional. It's how we get the browser (and curl, etc) to trust the local development site using https. But of course, we can just use all the various means we've always used to ignore untrusted connections. But mkcert makes it really nice!
Note that on Linux mkcert -install may give you some extra instructions that you'll need to do for everything to work right, see docs.
For me, I had to use chocolaty to get this in. Everything else kept failing..
choco install mkcert
OK, so this is my first SO question so I'm gonna try my best to lay this out.
I have a Windows 10 laptop on which I am trying to install gcc. I have in the past tried alternatives such as netbeans, cygwin and various emulators and virtual machines all to no avail.
What has been working so far is that I enabled the 'new' windows developer mode which allowed me to download a Linux bash shell from the windows store. It works for all the regular Linux commands, but doesn't have gcc installed.
When I type in gcc (or gcc --version) in the shell, it prints the following line:
The program 'gcc' is currently not installed. You can install it by typing:
sudo apt install gcc
Which I tried, it then ran through a bunch of installer stuff but consistently seemed to run into errors such as the following:
Err:7 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 libdpkg- >perl all 1.18.4ubuntu1.2
404 Not Found [IP: INSERT IP ADDRESS HERE ]
where the ip address is different on each error line.
It ultimately fails with the following line:
Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?
I have tried but again I get the same kinds of errors as above.
I would really like to get gcc working in the Windows/Linux shell as it is working great for everything else, and I'm trying to keep the number of programs on my computer to a minimum.
Does anyone know why this isn't working, or how (if possible) I can make it work?
P.S I do need it to be gcc because of school reasons
For what it's worth: I landed on this SO topic after having a similar issue.
What fixed it for me was to run
sudo apt-get update
sudo apt-get upgrade
I guess the repo URLs were too old, even though my Ubuntu was in a recent version.
I just ran into the same thing attempting to install python-pip. According to this article, this happens when you have the Windows 10 Anniversary Update (older) instead of the Creators update (newer). The solution is to either uninstall and re-install Ubuntu, or upgrade it (from 14.04 to 16.04). I found the upgrade to be simple and painless:
sudo do-release-upgrade
To check what you have, before and after via:
lsb_release -a
I had the same problem. Pinging the IP resulted in no response and visiting the website returned a 404.
I found a ppa with most current GCC and registered the PPA and was able to successfully install GCC with it; ppa website. I used GCC to build some software I wanted that was not found with apt-get.
From their page:
sudo add-apt-repository ppa:ubuntu-toolchain-r/test
sudo apt-get update
Try to run Ubuntu application in Windows with an option "Run as Administrator".