How to remove all docker containers in a network

Tim Salva — Thu, 08 Apr 2021 06:19:23 +0000

Update
Thanks @hasnayeen for making me aware of the following better approach

docker <stop|rm> $(docker ps -qf "network=<NAME>")

Steps

How to list docker containers in a network

Inspecting a docker network will list containers along with other information, we can use the --format flag to get a newline separated list.

docker network inspect <NAME> --format='{{range $id, $_ := .Containers}}{{println $id}}{{end}}

// Example output
197123ceff4c60ad99518e948047d842eab52ab7eac38476dabe22ac5f6cc209
2ec40124c66a394d6f29e1448bff3182902a94e74f923c7cab4f10c3d7f99d1d
aeb2b9d5686efcf186adf13ce6b8471782f332385aa8b2c4314932a1416f8376

Stopping and removing containers in a docker network

docker <stop|rm> $(docker network inspect <NAME> \
    --format='{{range $id, $_ := .Containers}}{{println $id}}{{end}}')

After much Googling I couldn't find how to do this anywhere, if there's a better way please let me know.

Makers Apprenticeship Boot Camp @ComparetheMarket 🐒 | My Experience 🤔

Tim Salva — Fri, 27 Dec 2019 11:24:02 +0000

Brief Context

About Me

I was in the last few months of Year 13, the final year of sixth-form, about to undergo my A-Level exams. Holding offers from a few universities, feeling pressured to uphold them. However, I eventually did decide to apply for a Software Engineering apprenticeship. Seven months later, I've now completed boot camp and thought I would write about my experiences so far.

What is Makers?

Taken straight from their website, makers.tech, they provide a '12 week, full-time, onsite course' to help you 'launch your software engineering career.' Most people will probably recognise them as Makers Academy, but they also have Makers Apprenticeships.

What is Compare the Market?

comparethemarket.com is a UK comparison website for car insurance, home insurance, energy, and more. I'm sure you've heard of Aleksandr Orlov, the meerkat.

Application Process

Overview of what I went through, from early-May when I first applied, up to mid-July when I received an offer. A process, lasting short of three months.

I applied online through CtM's parent company BGL Group; where I filled in a standard application form, alongside it sending my CV and other relevant details.

Once BGL approved my initial application, they scheduled me in for a telephone interview. Here I encountered a small hurdle, nobody called. It took me just over two weeks of trying to reach someone at BGL recruitment until someone emailed me back. Interview re-scheduled, first and the last hurdle overcome. The interview was non-technical, just asking about my reasons which led me to apply plus a series of questions acquiring a summary of who I am and my story.

Next, I had two weeks to complete a course on Ruby, the programming language, on Codecademy.

The second telephone interview was with Makers, still non-technical, similar to the first interview, but asking more questions about my coding background, if any.

Upon passing the second interview, I had to complete around eight small Ruby coding challenges on repl.it, having completed the Ruby course, I was equipped with the skills to succeed.

At last! I reached the final interview with BGL. It was a STAR based behavioural interview, where they were trying to gauge how I would act under specific situations.

After some overthinking and a one-week wait, I was relieved to find out I had gotten an offer. 😌

Boot Camp

The apprenticeship is twelve months long; the first three months you spend doing off the job training (boot camp). Usually, you have to travel to Makers headquarters in London; however, BGL Group and Makers have partnered up to bring the Makers experience up to Peterborough, where the company is situated. Throughout the opening twelve weeks, coaches from Makers were on rotation spending time with the eighteen of us.

Typically, each day broke up into two halves. The first, being your own time, working on what you desired and needed the most. The second, pair-programming with a randomly selected partner aiming to complete a set challenge spanning the day or more. On the last day of each week, we had a solo-challenge, a chance to put into action and test ourselves on new skills. Additionally, every day, there was optional meditation, a time to take a step back and relax for a few moments, an activity I frequently opted to benefit from early on. Once a week, there was also after-hours yoga, guided by an instructor that came into the office.

Following this agenda, we focused on a given topic for a set number of weeks. At a higher-level it went like this:

Week 1 - Git and command-line skills
Weeks 2 & 3 - Test-driven development
Weeks 4 & 5 - Object-oriented design
Week 6 - Web apps (databases, web app architectures...)
Week 7 - JavaScript

Occasional workshops supplemented self-learning. Coaches were also really good at making you feel like you could ask them for help if you ever got super stuck, and were always reachable on Slack.

Now that we knew the basics, it was time to practice working on a project in a team of four to five. The next set of weeks went like this:

Week 8 - Build a Clone of Airbnb
Weeks 9 & 10 - Build a Clone of Facebook
Weeks 11 & 12 - Final project (we decided what we wanted to make)

During team projects, coaches recommended ways of working. Ultimately, we, as a team, tailored the advice given to us and decided how we would function. We worked as mini agile teams, incorporating stand-ups, retros, sprints, and tickets with correlating user stories — a simulation of how we would be working for real.

On the last day, we got to present our final project to people from our company. It was a big day; there was pizza. 🍕

Takeaways

A few skills I'm proud of improving due to the boot camp are:

Git and the command line - every single day we had to use these skills, now it's almost second nature when it comes to basic manipulation and navigation via command line and everyday git operations
Pair programming - specifically the driver & navigator style, I got to see the thought processes of many other people as they went about solving a problem and I got to improve expressing technical ideas to another person
Test-driven development - TDD-ing required you to have a picture of how your code is going to be structured and how it would behave before writing the implementation. Often I recognised this improved the quality of what I wrote.
Taking action on initiative - Makers don't teach in a traditional school format, you're mostly just guided towards specific skills. Picking up a skill is primarily up to you, you have to put the work in yourself, googling the same thing like a hundred times, until finally, it clicks.
Working in a team - when you are working on a solo project, it's easy to make decisions, you have an idea, and you execute on it. Inside a team, there are many different ideas on how to accomplish many different things, working through the many approaches as a team and filtering them down to one is hard. When someone writes code in a different way than how you may have envisioned, you must let go of complete control, trust your team and move forward.

Next Steps

I've had such a great time so far, meeting tons of friendly and supportive people from both Makers and BGL. First three months are done, now I get to work for real at Compare the Market, striving towards bettering myself and finishing my apprenticeship. I honestly can't wait. 😁😃😆

This post is from blog.jtsalva.dev

Credit to Unspalsh.com ❤️ for images

DEV Community: Tim Salva