Vagrant doing weird, for some reason trying to run mkdir -p /tmp/vagrant-ansible/inventory (sudo=true) as sudo

Vagrant
1

DEBUG ssh: Exit status: 0
INFO guest: Detected: alma!
DEBUG guest: Searching for cap: ansible_installed
DEBUG guest: Checking in: alma
DEBUG guest: Checking in: redhat
DEBUG guest: Checking in: linux
DEBUG guest: Found cap: ansible_installed in linux
DEBUG ssh: Checking whether SSH is ready…
DEBUG ssh: Re-using SSH connection.
INFO ssh: SSH is ready!
DEBUG ssh: Re-using SSH connection.
INFO ssh: Execute: (sudo=false)
DEBUG ssh: stderr: 41e57d38-b4f7-4e46-9c38-13873d338b86-vagrant-ssh
DEBUG ssh: Exit status: 0
DEBUG guest: Searching for cap: ansible_installed
DEBUG guest: Checking in: alma
DEBUG guest: Checking in: redhat
DEBUG guest: Checking in: linux
DEBUG guest: Found cap: ansible_installed in linux
INFO guest: Execute capability: ansible_installed [#<Vagrant::Machine: appsrv01 (VagrantPlugins::ProviderVirtualBox::Provider)>, “”] (alma)
DEBUG ssh: Re-using SSH connection.
INFO ssh: Execute: test -x “$(command -v ansible)” (sudo=false)
DEBUG ssh: stderr: 41e57d38-b4f7-4e46-9c38-13873d338b86-vagrant-ssh
DEBUG ssh: Exit status: 0
DEBUG ssh: Re-using SSH connection.
INFO ssh: Execute: ansible --version (sudo=false)
DEBUG ssh: stderr: 41e57d38-b4f7-4e46-9c38-13873d338b86-vagrant-ssh
DEBUG ssh: Exit status: 0
DEBUG ssh: Re-using SSH connection.
INFO ssh: Execute: mkdir -p /tmp/vagrant-ansible/inventory (sudo=true)
DEBUG ssh: stderr:
We trust you have received the usual lecture from the local System
Administrator. It usually boils down to these three things:

#1) Respect the privacy of others.
#2) Think before you type.
#3) With great power comes great responsibility.

DEBUG ssh: stderr: sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper

DEBUG ssh: stderr: sudo: a password is required

DEBUG ssh: Exit status: 1
ERROR warden: Error occurred: The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

mkdir -p /tmp/vagrant-ansible/inventory

Stdout from the command:

Stderr from the command:

How can I work around this?

Thank you.