Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ubuntu 17.10 is EOL, and provisioning new box now fails as a result #414

Open
tmertz opened this issue Sep 5, 2019 · 7 comments
Open

Ubuntu 17.10 is EOL, and provisioning new box now fails as a result #414

tmertz opened this issue Sep 5, 2019 · 7 comments

Comments

@tmertz
Copy link

tmertz commented Sep 5, 2019

Essentially 'vagrant up --provision' fails because APT repos no longer exist.

Scotchbox should have been upgraded to 18.04 a long time ago. In fact, it kinda boggles the mind that a dev tool is not running on the LTS version of Ubuntu.

@Brendonwbrown
Copy link

Bumped by head against this yesterday.
I don't think we are getting any more support, especially for the free or scotch box.

Follow this to upgrade a box that is up to the latest LTS Ubuntu: https://www.linuxbabe.com/ubuntu/upgrade-ubuntu-16-10-17-04-to-ubuntu-18-04.
Check comments if you have an errors.

If you had a linux headers error with installing vbox guest tools, follow this to install latest linux kernel headers: https://www.cyberciti.biz/faq/installing-latest-stable-mainline-linux-kernel-on-ubuntu-with-apt-get/

Follow this guide to package your updated box: https://scotch.io/tutorials/how-to-create-a-vagrant-base-box-from-an-existing-one

Now you have your own local Scotch box updated to latest Long Term Support version.
You can even change the SSH graphics by following this guide. https://linuxconfig.org/how-to-change-welcome-message-motd-on-ubuntu-18-04-server

@reddingwebpro
Copy link

Since it seems like Nick has abandoned this product, I'd like to direct you to my variation called Cognac box, which you can find at: https://github.com/reddingwebpro/cognacbox

@kden13
Copy link

kden13 commented Mar 17, 2020 via email

@reddingwebpro
Copy link

reddingwebpro commented Mar 17, 2020 via email

@kden13
Copy link

kden13 commented Mar 17, 2020 via email

@kden13
Copy link

kden13 commented Mar 17, 2020 via email

@plutinolabs
Copy link

Not sure if you're still looking for a solution to our original problem @tmertz . I changed the repo location to point to the old ones. So provisioning shouldn't fail, but you'll be stuck with the old packages unless you jump through some hoops in your provisioning script.

I added the following to the start of my provision script to point to the old repo.

sed -i 's|archive.ubuntu.com|old-releases.ubuntu.com|g' /etc/apt/sources.list

But, like it has been said previous, I got tired of waiting for an update to the box and decided to make my own. If you're interested you can have a look here https://github.com/prefixstudio/merlot

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants