{"record":{"id":"54eb4db38b8ea06e","repo":"hashicorp/vagrant","slug":"the-box-you-re-attempting-to-add-doesn-t-support-t-54eb4d","errorCode":null,"errorMessage":"The box you're attempting to add doesn't support the requested\narchitecture with the current provider. The following providers\nsupport the requested architecture for this box:\n\n  %{supported_providers}\n\nIf the above providers cannot be used, please find and alternate\nbox that supports the requested architecture.\n\nBox: %{name}\nAddress: %{url}\nArchitecture: %{architecture}\nProvider: %{provider}","messagePattern":"The box you're attempting to add doesn't support the requested\narchitecture with the current provider\\. The following providers\nsupport the requested architecture for this box:\n\n  %(.+?)\n\nIf the above providers cannot be used, please find and alternate\nbox that supports the requested architecture\\.\n\nBox: %(.+?)\nAddress: %(.+?)\nArchitecture: %(.+?)\nProvider: %(.+?)","errorType":"exception","errorClass":"Vagrant::Errors::BoxAddNoMatchingArchitecture","httpStatus":null,"severity":"warning","filePath":"lib/vagrant/action/builtin/box_add.rb","lineNumber":301,"sourceCode":"\n              # If no versions are found, then the box does not provide\n              # support for the requested architecture using the requested\n              # architecture\n              if available_versions.empty?\n                supported_providers = metadata.versions(architecture: architecture).map do |v|\n                  metadata.version(v).providers(architecture)\n                end.compact.uniq.sort\n\n                # If no providers are found, then the box does not\n                # have any support for the requested architecture\n                if supported_providers.empty?\n                  raise Errors::BoxAddNoArchitectureSupport,\n                    architecture: display_architecture,\n                    name: metadata.name,\n                    url: display_url\n                end\n\n                raise Errors::BoxAddNoMatchingArchitecture,\n                  provider: Array(provider).join(\", \"),\n                  architecture: display_architecture,\n                  name: metadata.name,\n                  url: display_url,\n                  supported_providers: supported_providers\n              end\n\n              raise Errors::BoxAddNoMatchingProviderVersion,\n                constraints: version || \">= 0\",\n                provider: Array(provider).join(\", \"),\n                architecture: display_architecture,\n                name: metadata.name,\n                url: display_url,\n                versions: available_versions.reverse.join(\", \")\n            else\n              # Report that no version can match the constraints requested\n              # but show what versions are supported\n              raise Errors::BoxAddNoMatchingVersion,","sourceCodeStart":283,"sourceCodeEnd":319,"githubUrl":"https://github.com/hashicorp/vagrant/blob/35f3160f4ad6edc3a9f3aa9570adfc1a4d73aaa5/lib/vagrant/action/builtin/box_add.rb#L283-L319","documentation":"In rsync-auto (rsync_auto.rb:69-74), the watcher compares the synced folders cached at last boot (`synced_folders(machine, cached: true)`) against a fresh read of the current Vagrantfile. When the fresh config contains folders the cached set does not (diff[:added] non-empty), it warns \"New synced folders were added to the Vagrantfile since running `vagrant reload`. If these new synced folders are backed by rsync, they won't be automatically synced until a `vagrant reload` is run.\" The watcher then iterates only the cached folders, so additions are ignored for the lifetime of the process.","triggerScenarios":"Editing the Vagrantfile to add an rsync synced folder (or starting rsync-auto against a machine whose data-dir cache predates recent Vagrantfile edits), then running `vagrant rsync-auto` — the cached-vs-fresh diff shows the addition and the warning prints once per machine per start.","commonSituations":"Developer adds a folder while rsync-auto is already running (or after `vagrant up` but before any reload) and wonders why edits never reach the guest; multi-machine Vagrantfiles where one machine got new folders; stale .vagrant cache after aborted reloads.","solutions":["Stop rsync-auto (Ctrl-C), run `vagrant reload` to re-baseline the cached synced folders, then restart `vagrant rsync-auto`.","If a reload is not convenient right now, push once manually with `vagrant rsync <machine>` and schedule the reload.","Confirm the baseline afterwards: restart rsync-auto and check the warning no longer appears and 'Watching: <path>' lists the new host path."],"exampleFix":"# before (warning: new synced folders were added...)\n#   Vagrantfile edited to add a folder, then:\nvagrant rsync-auto\n\n# after\nvagrant reload && vagrant rsync-auto","handlingStrategy":"validation","validationCode":"# After any Vagrantfile folder edit, re-baseline before watching:\nvagrant reload && vagrant rsync-auto","typeGuard":null,"tryCatchPattern":null,"preventionTips":["Make `vagrant reload` part of the workflow whenever synced folders are added or changed.","Restart rsync-auto after Vagrantfile edits — a running watcher never picks up new folders.","Use the 'Watching: <path>' startup lines to confirm every rsync host path is actually being monitored."],"tags":["rsync","vagrant","rsync-auto","synced-folders","reload"],"backgroundTag":"stale-config-reload-required","analyzedSha":"35f3160f4ad6edc3a9f3aa9570adfc1a4d73aaa5","analyzedAt":"2026-08-21T13:34:32.514Z","schemaVersion":2},"datasetVersion":"2026-08-21T18:17:14.833Z"}