search

sandervanvugt / cka

394 stars 510 forks source link

issues as soon as I issue vagrant up. #14

Open kzpl1 opened 1 year ago

kzpl1 commented 1 year ago

Need help with the following after running vagrant up. PLEASE. START ERROR control: 2023-02-22 15:58:40 (1.60 MB/s) - ‘go1.13.linux-amd64.tar.gz’ saved [120050424/120050424] control: control: + tar -C /usr/local -xzf go1.13.linux-amd64.tar.gz control: + git clone https://github.com/Mirantis/cri-dockerd.git control: Cloning into 'cri-dockerd'... control: + cd cri-dockerd/src control: /tmp/vagrant-shell: line 90: cd: cri-dockerd/src: No such file or directory control: + cd .. control: + install -o root -g root -m 0755 bin/cri-dockerd /usr/local/bin/cri-dockerd control: install: cannot stat ‘bin/cri-dockerd’: No such file or directory The SSH command responded with a non-zero exit status. Vagrant assumes that this means the command failed. The output for this command should be in the log above. Please read the output to determine what went wrong. END ERROR

/home/vagrant/cri-dockerd exists but /home/vagrant/cri-dockerd/src doesn't.

sandervanvugt commented 1 year ago

Use my setup-container.sh script, that works.

On 22 Feb 2023, at 09:42, kzpl1 @.***> wrote:

Need help with the following after running vagrant up. PLEASE. control: 2023-02-22 15:58:40 (1.60 MB/s) - ‘go1.13.linux-amd64.tar.gz’ saved [120050424/120050424] control: control: + tar -C /usr/local -xzf go1.13.linux-amd64.tar.gz control: + git clone https://github.com/Mirantis/cri-dockerd.git https://github.com/Mirantis/cri-dockerd.git control: Cloning into 'cri-dockerd'... control: + cd cri-dockerd/src control: /tmp/vagrant-shell: line 90: cd: cri-dockerd/src: No such file or directory control: + cd .. control: + install -o root -g root -m 0755 bin/cri-dockerd /usr/local/bin/cri-dockerd control: install: cannot stat ‘bin/cri-dockerd’: No such file or directory The SSH command responded with a non-zero exit status. Vagrant assumes that this means the command failed. The output for this command should be in the log above. Please read the output to determine what went wrong.

— Reply to this email directly, view it on GitHub https://github.com/sandervanvugt/cka/issues/14, or unsubscribe https://github.com/notifications/unsubscribe-auth/AG3TNVSQNBI3DDQGEKJK3UTWYZFYJANCNFSM6AAAAAAVEUHH34. You are receiving this because you are subscribed to this thread.

kzpl1 commented 1 year ago

Please be patient with my ignorance.

  1. I first run "vagrant up". After that, the VMs get created up to control and worker{1..3} and it fails with the above output.
  2. I "vagrant ssh control" to get into the vm and run the "setup-container.sh" script. I went ahead and ran the script and nothing happened. Please steer me to what I am doing wrong. I am running Git and Oracle Virtualbox on Windows 10.