How to tell a Docker client to communicate with a remote Docker daemon

In this episode, I discuss how the Docker client communicates with the Docker daemon, how I came to re-learn this essential fact while building a CD workflow in GitHub Actions recently, and how it helped me overhaul the final chapter of the Docker Essentials book and course.

Show Notes

While building my first GitHub Action-based workflow recently, I struggled until I took the time to relearn - and re-appreciate - how the Docker client and daemon communicate. In this episode, I share:

• How they work
• How the understanding helped me build a solid workflow to deploy webdevwithmatt.com
• Some of the different ways you can tell the Docker client which Docker daemon (remote engine) to communicate with
• plus lots more

Links from the episode

• Docker Overview
• "How to deploy on remote Docker hosts with docker-compose" from the Docker blog
• Digital Ocean Container Registry
• GitHub Actions documentation
• Docker Essentials (book and course)
• My Pluralsight courses

Hosted and produced by: Matthew Setter.

Website: https://webdevwithmatt.com
Follow us on: Twitter, Instagram, and LinkedIn.

If you like the podcast, and want to support it, how about buying me a coffee?

★ Support this podcast on Patreon ★

What is Web Dev with Matt?

Want to learn web development from the comfort of your chair, car, when you're out for a run, or doing some random house work? This is the show for you. Every week, in 20 - 40 minutes, I help you improve your web development skills with new knowledge, tips, pointers, random facts, inspiration, and some general chit chat. Tune in to have a fun, engaging, and friendly conversation about web development.