1. 3
  1.  

  2. 6

    It’s a curiosity to me that people using Vagrant in 2017 continue to use the “precise64” image. It’s Ubuntu 12.04 - a release from 5 1/2 years ago.

    1. 5

      Mind you that is EOL since April 2017. A few years ago when I was using Vagrant one knew to use Trusty (14.04 LTS) or Xenial (16.04 LTS) just to have something reasonably current. Now it’s a matter of security patches, 6 CVEs since April.

      1. 3

        The official docs still refer to it, that is probably why.

        1. 1

          Yes, that is why. Some of the available boxes lack installed guest additions, which is necessary for synced folders. Guest additions isn’t too hard to install, but I figured I would go with a box that I knew already had guest additions installed. It was just something I wanted to avoid during the post.

          At work we use CentOS 7, and it lacked guest additions so I had to take the time to build a new version of the CentOS 7 box with guest additions installed.

          1. 1

            I use our own debian boxes for most work, but there should be bento boxes for most major distros/versions.

            There should be very little need for “end users” to build their own boxes from scratch.

        2. 2

          Because hashicorp/precise64 used to be the only hashicorp box supporting the most important providers, and the corresponding pull request has been closed without actually updating the docs later.

          https://github.com/hashicorp/vagrant/pull/8817

        3. 1

          While this would likely help some people, it really feels more like “How to set up a basic vagrant development environment” than at all Erlang related to me, honestly.