Describe the bug
When the proper commands are run to generate a worker with the right dependencies, ie. python3, workers generate etc.. the vagrant workers up command fails at the end of the machine generation due to a gpg keygen for NodeJS asking for a tty that doesn't actually exist. Source: Submitty/.config/distro_setup/22.04/setup_distro.sh on line 79
Expected behavior
The worker machine should generate and configure itself to be set up and ssh-able. The gpg keygen should work, also.
To Reproduce
Steps to reproduce the behavior:
according to guide
- make sure proper dependencies are installed
- run
vagrant workers generate , and the configuration file should be made without a hitch.
- run
vagrant workers up, and it should fail near the last step of configuration.
- See error
Configuration
- OS: Arch linux, Windows 11
- Browser N/A
Screenshots
Additional context
Describe the bug
When the proper commands are run to generate a worker with the right dependencies, ie. python3, workers generate etc.. the
vagrant workers upcommand fails at the end of the machine generation due to a gpg keygen for NodeJS asking for a tty that doesn't actually exist. Source:Submitty/.config/distro_setup/22.04/setup_distro.shon line 79Expected behavior
The worker machine should generate and configure itself to be set up and ssh-able. The gpg keygen should work, also.
To Reproduce
Steps to reproduce the behavior:
according to guide
vagrant workers generate, and the configuration file should be made without a hitch.vagrant workers up, and it should fail near the last step of configuration.Configuration
Screenshots
Additional context