Configuring the dev environment can be difficult. One example is this blog, it requires ruby, some “"”amazing””” rubygems, etc. configuring it in MacOS is hard, in Windows is directly a nightmare. Recently, I tried to write a post from a new laptop, the moment I saw I could not build the jekyll site I desisted. I pushed to a branch and built in another machine. Then I learned about Visual Studio Code Dev Containers.
Automate Dev Container creation 🤖
So can I configure a container and build my blog directly there? Can I forget about configuring Jekyll in each machine I want to blog from? Yes you can!
Ok cool, but how do I configure the container? that will be hard! well, I have good news, there are predefined examples and the Jekyll one works out of the box. Check the documentation, you just need to:
- Open Command Palette (
Dev Containers: Add Dev Container Configuration Files
- Look for the
I don’t have Docker Desktop
One of the requirements to run VS Code Dev Containers is having Docker Desktop. If you don’t have it and you are using a Mac, I got you covered, meet Colima.
Steps to install:
- Uninstall previous Docker Desktop App and related files. If you used brew to install, you can use:
brew uninstall --cask docker
- Then run
brew install colima
- Install dependencies
brew install docker docker-compose
- Finally run it
And that’s it, VS Code Dev Containers will works flawlessly. Be aware Colima by default uses 2 CPUs, 2GiB memory and 60GiB storage but this can be configured.
Once you get into the container there is no git anymore => To solve it, run
git status. It will suggest a command like
git config --global --add safe.directory /path/to/repo. Run it and git will be back.
I’ll keep an any for more automated containers, they can be super helpful when the environment configuration is complex. Are you planning to use it for any of your projects?