hashicorp/vagrant · error

vagrant.actions.disk.provider_unsupported

Error message

vagrant.actions.disk.provider_unsupported

What it means

Error "vagrant.actions.disk.provider_unsupported" thrown in hashicorp/vagrant.

Source

Thrown at lib/vagrant/action/builtin/disk.rb:25

  module Action
    module Builtin
      class Disk
        def initialize(app, env)
          @app    = app
          @logger = Log4r::Logger.new("vagrant::action::builtin::disk")
        end

        def call(env)
          machine = env[:machine]
          defined_disks = get_disks(machine, env)

          # Call into providers machine implementation for disk management
          configured_disks = {}
          if !defined_disks.empty?
            if machine.provider.capability?(:configure_disks)
             configured_disks = machine.provider.capability(:configure_disks, defined_disks)
            else
              env[:ui].warn(I18n.t("vagrant.actions.disk.provider_unsupported",
                                 provider: machine.provider_name))
            end
          end

          # Always write the disk metadata even if the configured
          # disks is empty. This ensure that old entries are not
          # orphaned in the metadata file.
          write_disk_metadata(machine, configured_disks)

          # Continue On
          @app.call(env)
        end

        def write_disk_metadata(machine, current_disks)
          meta_file = machine.data_dir.join("disk_meta")
          @logger.debug("Writing disk metadata file to #{meta_file}")
          File.open(meta_file.to_s, "w+") do |file|
            file.write(JSON.dump(current_disks))

View on GitHub (pinned to 35f3160f4a)

When it happens

Trigger: Thrown at lib/vagrant/action/builtin/disk.rb:25 when the library encounters an invalid state.

Common situations: See trigger scenarios.

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