rails / rails-dev-box

A virtual machine for Ruby on Rails core development
MIT License
2.05k stars 580 forks source link

Prevent interactive on provisioning #172

Closed sergioisidoro closed 4 years ago

sergioisidoro commented 4 years ago

When installing Ruby on provisioning it would hang completely

I think it was because a prompt is blocking installation

Screenshot 2019-12-23 at 10 43 16

DEBIAN_FRONTEND=noninteractive should prevent interactive during provisioning

Note that this happens regardless of using the -y flag on apt-get

sergioisidoro commented 4 years ago

PS: This might have been related to this Ubuntu bug: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1832919

fxn commented 4 years ago

I have just provisioned a new VM without using this environment variable. The base box ubuntu/disco64 got updated to version v20191217.0.0, though, I do not know if that made a difference.

As you noted, theapt-get command includes the -y flag which according to the documentation implies non-interactive mode:

-y, --yes, --assume-yes
  Automatic yes to prompts. Assume "yes" as answer to all prompts and run
  non-interactively. If an undesirable situation, such as changing a held package
  or removing an essential package, occurs then apt-get will abort.

And this has worked fine for years.

Could you please update the base box and see if provisioning completes for you too?

sergioisidoro commented 4 years ago

@fxn yeah, this was really strange. I've had this env working fine before. I think it was the update to VirtualBox 6.x that caused the problems.

I had some other trouble with disco64, so I downgraded it to bionic, and that's when I got this issue. All this started when migrating to VirtualBox 6.x

I think this is really some problem upstream. And the common denominator seems to always be libssl:

I can re-test everything to see if I can replicate the issue.

To be clear: this is more of a workaround before things are fixed wherever they are broken. Setting DEBIAN_FRONTEND is, as I understood, not recommended.

Edit: Some more references, although they say the issue has been patched. https://github.com/hashicorp/vagrant/issues/10914 I think I specified the image version to test this, but I'll double check

sergioisidoro commented 4 years ago

Ok, I just retried everything, and to be sure I purged the image and re-downloaded it.

└─▪vagrant box remove ubuntu/disco64                                                                                                                                                                                                                                                          
Removing box 'ubuntu/disco64' (v20191217.0.0) with provider 'virtualbox'...      

Seems to have worked... Possibly my problem was in the cached image? Or the problem got fixed? I don't know :)

fxn commented 4 years ago

Thanks for reporting it anyway!