Honestly enjoyed this process, usually tutorials/walkthroughs can take a lot of your time when they're new to you. Started out with this learning guide right after the installing Docker. Short , sweet and simple is the best way to describe how they packaged this. You will find more documentation as you start getting to specific parts of the walkthroughs which will be good to read on.
- What is a container?
- How do I run a container?
- Run Docker Hub images
- Multi-container applications
- Persist your data between containers
- Access your local folder from a container
- Containerize your application
- Publish your image
So the cool thing about this section is that they actually create a welcome container for you? I mean like huuh? I already created my first container just by clicking on a guide? sorcery.
This section was pretty straight forward , there wasn't much weird things happening when I tried this out.
Learn how to run your own one now. You will have to clone a repo. What if you dont know how to clone a repo?
Here's some docs: Cloning a repo
You will also find yourself in the IDE of your choosing, checking out some code. I mentioned before, due to the tutorial giving off a Visual Studio Code vibes only, I went that route.
SOME CHEATCODES (Assuming you have GIT installed)
| Step 1 | Step 2 |
|---|---|
 Once inside your welcome-to-docker folder type cmd in the top bar |
 After hitting Enter, you will have the command line open then type in code . which will open the IDE |
Have a browse through the files that the tutorial will be taking you through, especially the breakdown of commands for the terminal
In this section you will start seeing some things that will make more sense as you go about.
This is where things start getting spicy, it goes from just being one container to many containers with only one command, Introducing a tool known as Docker Compose. I feel like whenever something gets compose added next to it , immediately it becomes "oh look at me , I can do so much more"
Also make sure that if you dont copy and paste commands for whatever reason and type them out manually, be sure that these commands are TO THE T, sometimes I felt abit like "ahh let me rather type this and boom error , only to see its a typo".
There will be some docs for compose watch documnentation
Don't be afraid to delete it.. there's a reason for everything.
In otherwords , how can I make the information that's inside my database stubborn? Kinda like Insurance Agents, just because you cancelled your policy with one , does not mean another wont call having your exact info(super werid). You will be introduced to volumes. Some hot-keys for the Windows users, you will be uncommenting some code. Highlight the code that has been commented out then ctrl + k & then ctrl + u, this will uncomment the highlighted section. Remember to have a look at the text that are under the code boxes too in the guides, these are gold.
Things to note:
- Once code is uncommented , run the project again in terminal
- Make sure that volume is mentioned within terminal output after command
- To test if data persists , add some tasks first
- Delete the multi container
- Then build again and see your stubborn data
- Dont forget to save files in IDE (Trust me)
Bind Mounts ? WHAT ARE THOOOSE !? It's like a direct link between your computer and a container. It lets the container access files or folders from your computer. In this section you will be uncommenting some code too. Don't forget to save your work as soon as you make any changes with ctrl + s, Pay close attention to the outputs coming from your terminal , for some reason its just good to know whats coming out of it. Personally I would just look at what's actually running. You will notice there are some links being added in your guide which provides the port http://localhost:3001/ note that these ports are the ones specified for you repos that you working in , so you can click these within you Docker Desktop to open the browser.
When you get to this part , things will start to make abit more sense I hope? You'll be seeing how Docker comes together from a command called docker init which will create all the files required for you. I got abit hands on with this. Decided to create my own Web App on using the .NET. Now that I'm looking looking at this section , I realized , they dont actually provide you a repo for this specific section, which is okay , because you could use mine too? docker web app example
This is a pretty simple one, Im guessing this is the happy path of whats already available within your docker desktop , I have noticed that some of the homies had some issues when it came to the image part of docker but not this specific path , its more in the developing path when you actually incorporating docker in real projects. You will be renaming your image so you can publish it to the docker hub.
for this you could use the docker desktop terminal
you can use the welcome-to-docker you had from the start to do this section
Now that you've had some fun with docker , why not try out their language specific guides? The guide I went for was the .NET
.NET language-specific guide