You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
# -*- mode: ruby -*-
# vi: set ft=ruby :
# Vagrantfile API/syntax version. Don't touch unless you know what you're doing!
VAGRANTFILE_API_VERSION = "2"
Vagrant.configure(VAGRANTFILE_API_VERSION) do |config|
config.vm.define "linux64-musl" do |musl64|
musl64.vm.box = "alpine/alpine64"
musl64.vm.box_version = "3.6.0"
musl64.vm.provision :shell, path: "build-linux-alpine.sh"
end
config.vm.define "linux32-musl" do |musl32|
musl32.vm.box = "alpine/alpine32"
musl32.vm.box_version = "3.6.0"
musl32.vm.provision :shell, path: "build-linux-alpine.sh"
end
config.vm.synced_folder "../..", "/rocksdb", type: "rsync"
end
Then run vagrant up linux64-musl and eventually you see the error:
==> linux64-musl: Installing rsync to the VM...
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!
apk add rsync
Stdout from the command:
# -*- mode: ruby -*-
rsync (missing):
required by: world[rsync]
Stderr from the command:
WARNING: Ignoring APKINDEX.066df28d.tar.gz: No such file or directory
WARNING: Ignoring APKINDEX.b53994b4.tar.gz: No such file or directory
ERROR: unsatisfiable constraints:
This issue - maier/vagrant-alpine#29 seems to explain that rsync cannot be installed without first doing either an apk update or apkSHOULD use --no-cache.
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
Vagrantfile:
Then run
vagrant up linux64-musl
and eventually you see the error:This issue - maier/vagrant-alpine#29 seems to explain that
rsync
cannot be installed without first doing either anapk update
orapk
SHOULD use--no-cache
.I think this might also be related to #9574
The text was updated successfully, but these errors were encountered: