Docker
Docker is the big name in "containerization". The big idea behind Docker and other container technologies is that they allow us to package our programs with an environment and ship the whole thing. Most real world programs don't work in isolation, they need:
- Files from disk
- Environment variables
- Installed dependencies
- Specific permissions
Docker images and containers have become a standard for deploying applications. In this course, you'll learn all about Docker and containerization.
Boot.dev CLI
Throughout this course, you'll be using the Boot.dev CLI to run our tests (which are just CLI commands) against your local environment. Install it now if you don't already have it. All the instructions and troubleshooting info are on the GitHub page.
Make sure the Boot.dev CLI install worked:
bootdev --version
If you're stuck, reach out in the help forums of the Discord.
Once the bootdev command is working, log in and follow the instructions:
bootdev login
Run vs. Submit
Lessons have a series of "commands" that run on your local machine, and a series of tests it will check against the results of the command. There are two ways to run these commands: run and submit:
bootdev run <id>: This will run the commands and show you the results. It's to be used for debugging, but it won't tell you whether or not you've passed the tests explicitly.bootdev run <id> -s: This will run the commands and give you pass/fail feedback. It will also mark the lesson as complete on the website. If you get it wrong however, you'll potentially lose your sharpshooter spree, so be sure to userunfirst!
You can copy the run/submit commands with the id ready-to-go from the test panel.
Assignment
Once you have the CLI installed and you're logged in, copy and paste the run command from the right into your terminal and execute it. If it's doing what you'd expect (printing it works on my machine), then run the submit command.