Configure Error while trying to build latest operating system

[upwindtec]

Describe the issue you are experiencing

I am trying to build the latest version of the operating system in order to test a kernel module that we developed. The build is done under Debian 12:
Linux debian12 6.1.0-37-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.140-1 (2025-05-22) x86_64 GNU/Linux

The command line used to run the build:
sudo scripts/enter.sh make generic_x86_64

The error I receive:

checking whether mknod can create fifo without root privileges... configure: error: in `/build/output/build/host-tar-1.35':
configure: error: you should not run configure as root (set FORCE_UNSAFE_CONFIGURE=1 in environment to bypass this check)

The error persists even with FORCE_UNSAFE_CONFIGURE set to 1. Most articles I could find online recommend to build buildroot without elevated privileges, but the home assistant build does require root privileges. Executing the same command as a regular user errors out right away:
support/scripts/br2-external: line 52: /build/output/.br2-external.mk: Permission denied

What I am missing?

What operating system image do you use?

generic-x86-64 (Generic UEFI capable x86-64 systems)

What version of Home Assistant Operating System is installed?

16.2

Did the problem occur after upgrading the Operating System?

No

Hardware details

Debian 12 running under VMware virtual machine, itself running under Windows 10

Steps to reproduce the issue

1. Follow the steps from the developer documentation at https://developers.home-assistant.io/docs/operating-system/getting-started
2. git clone https://github.com/home-assistant/operating-system/ cd operating-system/ git submodule update --init
3. Checked that docker is installed and running properly
4. Checked that FORCE_UNSAFE_CONFIGURE is set to 1 : printenv FORCE_UNSAFE_CONFIGURE
5. Started the build with sudo scripts/enter.sh make generic_x86_64...

Anything in the Supervisor logs that might be useful for us?

N/A

Anything in the Host logs that might be useful for us?

N/A

System information

No response

Additional information

No response

[sairon]

Remove the output directory (as root) and do not run scripts/enter.sh with sudo. Also make sure you're in the docker user group, i.e. you can execute docker run without using sudo. I see that it's incorrect in the developer docs, will open a PR to fix that.

[upwindtec]

Thank you for your prompt reply. I followed your instructions and the build is running just fine.