))
How to tell a Docker client to communicate with a remote Docker daemon
Manage episode 305804479 series 3000439
Indhold leveret af Matthew Setter. Alt podcastindhold inklusive episoder, grafik og podcastbeskrivelser uploades og leveres direkte af Matthew Setter eller deres podcastplatformspartner. Hvis du mener, at nogen bruger dit ophavsretligt beskyttede værk uden din tilladelse, kan du følge processen beskrevet her https://da.player.fm/legal.
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 ★22 episoder
Del
