@s4l3h1, thanks for your PR! By analyzing the history of the files in this pull request, we identified @moshekaplan to be a potential reviewer.

@moshekaplan Sup dude?

@mention-bot This pull request doesn't reviewed yet!!!!

The following 'error message' appears when building CRITs with the Dockerfile:

debconf: unable to initialize frontend: Dialog
debconf: (No usable dialog-like program is installed, so the dialog based frontend cannot be used. at /usr/share/perl5/Debconf/FrontEnd/Dialog.pm line 76, <> 
line 48.)
debconf: falling back to frontend: Readline
debconf: unable to initialize frontend: Readline
debconf: (This frontend requires a controlling tty.)
debconf: falling back to frontend: Teletype
dpkg-preconfigure: unable to re-open stdin: 

This error message is completely harmless. Setting DEBIAN_FRONTEND to noninteractive is purely a cosmetic change.

Additionally, setting ENV DEBIAN_FRONTEND noninteractive in the Dockerfile is dangerous because the environment variable persists after the build.

Docker also includes information in their FAQ regarding the use of DEBIAN_FRONTEND=noninteractive: https://docs.docker.com/engine/faq/#why-is-debian_frontendnoninteractive-discouraged-in-dockerfiles

There is also a discussion on Github regarding a safer alternative to ENV DEBIAN_FRONTEND noninteractive
moby/moby#4032 (comment)
moby/moby#4032 (comment)

To suppress the 'error message' safely, the following change could be made to the Dockerfile:

RUN DEBIAN_FRONTEND=noninteractive TERM=xterm sh ./script/bootstrap < docker_inputs