hashicorp/vagrant · info · Vagrant::Errors::BoxAddNoMatchingProvider

The box you're attempting to add doesn't support the provide

Error message

The box you're attempting to add doesn't support the provider
you requested. Please find an alternate box or use an alternate
provider. Double-check your requested provider to verify you didn't
simply misspell it.

If you're adding a box from HashiCorp's Vagrant Public Registry, make sure the box is
released.

Name: %{name}
Address: %{url}
Requested provider: %{requested}

What it means

In the `vagrant rsync` command loop (rsync.rb:41-53), if the provider implements the proxy_machine capability and returns a non-nil proxy machine, Vagrant warns "The provider ('%{provider}') for the machine '%{name}' is using a proxy machine. RSync will sync to this proxy instead of directly to the environment itself." and reassigns machine = proxy so all rsync targets (hostpaths/guestpaths) resolve against the proxy VM. This is informational, expected behavior for providers that run environments inside a helper VM — classically the Docker provider proxying to its boot2docker/host VM.

Source

Thrown at lib/vagrant/action/builtin/box_add.rb:272

          if env[:box_name] && metadata.name != env[:box_name]
            raise Errors::BoxAddNameMismatch,
              actual_name: metadata.name,
              requested_name: env[:box_name]
          end

          metadata_version  = metadata.version(
            version || ">= 0",
            provider: provider,
            architecture: architecture,
          )

          if !metadata_version
            if provider
              # If no version found that supports the provider, then the
              # box has no support for the provider
              if !metadata.version(">= 0", provider: provider)
                raise Errors::BoxAddNoMatchingProvider,
                  name: metadata.name,
                  requested: Array(provider).join(", "),
                  url: display_url
              end

              # Get all versions that support the provider and architecture
              available_versions = metadata.versions(
                provider: provider,
                architecture: architecture
              )

              # If no versions are found, then the box does not provide
              # support for the requested architecture using the requested
              # architecture
              if available_versions.empty?
                supported_providers = metadata.versions(architecture: architecture).map do |v|
                  metadata.version(v).providers(architecture)
                end.compact.uniq.sort

View on GitHub (pinned to 35f3160f4a)

Solutions

1. Treat it as informational — rsync is deliberately targeting the proxy VM that hosts your environment.
2. Confirm the synced folder content landed where the container expects it: `vagrant docker-ssh` (or ssh into the proxy VM) and inspect the guestpath.
3. If the proxy redirection is unexpected, check that you are not accidentally targeting a docker-provider machine; address machines by name: `vagrant rsync <name>`.

# Know your topology before syncing: providers with a proxy_machine capability
# (e.g. docker provider on a host VM) redirect rsync to the proxy.
vagrant status   # confirm which provider backs each machine
vagrant rsync --help  # then target explicitly: vagrant rsync <name>

# Where you hold a machine object
def rsync_redirected?(machine)
  return false unless machine.provider.capability?(:proxy_machine)
  !machine.provider.capability(:proxy_machine).nil?
end

When it happens

Trigger: Running `vagrant rsync [name]` on a machine whose provider returns a proxy from the proxy_machine capability — e.g. docker-provider containers backed by a docker-machine/Hyper-V/WSL2 helper VM, where the rsync destination must be the VM hosting the container rather than the container itself.

Common situations: Docker provider on macOS/Windows where containers run inside a proxy VM; users surprised that rsync output references a different machine name; harmless but worth confirming the proxy VM actually mounts the expected guestpath.

Related errors

• The box you're attempting to add doesn't support the request
• The box you're attempting to add doesn't support the request
• The box you're attempting to add has no available version th
• The synced folder type '%{type}' is reporting as unusable fo
• No synced folder implementation is available for your synced

AI-assisted analysis of hashicorp/vagrant@35f3160f4a (2026-08-21). Data as JSON: /api/errors/f499a3241864e4b2. Report an issue: GitHub.