[Bug]: vagrant up doesn't work

[Gekko0114]

Bug Description

When I run vagrant up, following error happens.
I think this is due to Vagrantfile because Vagrantfile.containerd2youki can be executed.

Bringing machine 'default' up with 'virtualbox' provider...
==> default: Box 'fedora/33-cloud-base' could not be found. Attempting to find and install...
    default: Box Provider: virtualbox
    default: Box Version: >= 0
==> default: Loading metadata for box 'fedora/33-cloud-base'
    default: URL: https://vagrantcloud.com/api/v2/vagrant/fedora/33-cloud-base
==> default: Adding box 'fedora/33-cloud-base' (v33.20201019.0) for provider: virtualbox
    default: Downloading: https://vagrantcloud.com/fedora/boxes/33-cloud-base/versions/33.20201019.0/providers/virtualbox/unknown/vagrant.box
Download redirected to host: download.fedoraproject.org
An error occurred while downloading the remote file. The error
message, if any, is reproduced below. Please fix this error and try
again.

The requested URL returned error: 404

Steps to Reproduce

run vagrant up
Maybe this is specific to my PC (mac apple m3). If vagrant up works for most of devs, please ignore this issue.

Expectation

No response

System and Setup Info

No response

Additional Context

No response

[YJDoc2]

Hey, this is probably because the box is not actually present on vagrant cloud. We usually use the containerd or podman test boxes, so the default seems to be out-of-date. You can copy over the config from other vagrant files or update the box to version 38 or 40.

[YJDoc2]

I have also opened #2890 for standardizing the vagrant files, so we do not run into issues like this.