I help indie authors transform their manuscripts into print-ready books. KDP | Print & eBook Formatting. Pivoting to DevOps and sharing my journey daily.
Over ten years ago, I was running Linux on my personal PC, editing boot menu entries, hopping distros. I even had Android x86 running for fun on my PC.
I was that tech guy.
Then life pulled me sideways.
So far, I've learnt these best practices for using Docker
Use official docker images as base image
Use specific image versions
Use small-sized official images
Optimise caching image layers
Finally got hands-on with Docker after three days of theory. Today was all about breaking and fixing things.
Containerised the funded startup finder app on a GCP Ubuntu VM. Wrote a multi-stage Dockerfile so the final image only carries what it needs to run.
@GreatnessDZN Yes. 80% of all my work as a freelancer have been from cold DMs I sent.
Although I left freelancing for a while, I'm coming back and I've resumed sending cold DMs. The only other option will be running ads.
Can't lie, it was a scrappy first hands-on Docker session today, but I learnt a lot. The plan is to tear everything down and start fresh, right from pulling the project from GitHub.
Finally got hands-on with Docker after three days of theory. Today was all about breaking and fixing things.
Containerised the funded startup finder app on a GCP Ubuntu VM. Wrote a multi-stage Dockerfile so the final image only carries what it needs to run.
Today was another heavy theory day on Docker, and I covered a lot of ground.
Learnt how to create custom Dockerfiles, the file structure and best practices for optimising image layers.
The project is live over HTTP (for a short time) on the VM's public IP, as I shared in my earlier post. HTTPS isn't set up yet, and I haven't pushed to Docker Hub either. Wanted to prioritise getting it live first.
Wrapped up with Docker Compose, including file structure, commands and how to write a Compose file for running multiple containers together.
Thatโs enough theory for me. My next session will be fully hands-on. Itโs time to practise all Iโve learnt in the past three days.
Today was another heavy theory day on Docker, and I covered a lot of ground.
Learnt how to create custom Dockerfiles, the file structure and best practices for optimising image layers.
Finally started Docker. Over three weeks behind schedule, but here we are.
Spent the past two days on the fundamentals: what containerisation is, what containers are and how they differ from virtual machines.
Also covered data persistence with named volumes and bind mounting. When a container stops, any data inside it is gone by default. Named volumes and bind mounting are the two ways to keep data alive beyond a container's lifecycle.
I havenโt gotten hands-on yet. I want to make sure I understand the concepts properly before jumping into the terminal. Looking forward to getting into the practical side ASAP.
Finally started Docker. Over three weeks behind schedule, but here we are.
Spent the past two days on the fundamentals: what containerisation is, what containers are and how they differ from virtual machines.
My DevOps journey Day 28 recap.
Been inconsistent lately due to a book formatting & cover design project I've been working on. But yesterday was a good one.
I also went through basic Docker commands, how to set up Docker on a Linux machine on AWS, using Docker Compose to run multiple containers, building Docker images and working with Dockerfiles.