Podcast appearances and mentions of solomon hykes

Solomon most famously created Docker and now runs Dagger… which has something special to share with you on Thursday. Catch Dagger at: - Tuesday: Dagger's workshop https://www.ai.engineer/schedule#ship-agents-that-ship-a-hands-on-workshop-for-swe-agent-builders - Wednesday: Dagger's talk: https://www.ai.engineer/schedule#how-to-trust-an-agent-with-software-delivery - Thursday: Solomon's Keynote https://www.ai.engineer/schedule#containing-agent-chaos Chapters 00:00 Introduction & Guest Background 00:29 What is Dagger? Post-Development Automation 01:08 Dagger's Community & Platform Engineers 02:32 AI Agents and Developer Workflows 03:40 Environment Isolation & The Power of Containers 06:28 The Need for Standards in Agent Environments 07:25 Design Constraints & Challenges for Dev Environments 11:26 Limitations of Current Tools & Agent-Native UX 14:11 Modularity, Customization, and the Lego Analogy 16:24 Convergence of CICD and Agentic Systems 17:41 Ephemeral Apps, Resource Constraints, and Local Execution 21:01 Adoption, Ecosystem, and the Role of Open Source 23:30 Dagger's Modular Approach & Integration Philosophy 25:38 Looking Ahead: Workshops, Keynotes, and the Future of Agentic Infrastructure

Dans cet épisode exceptionnel de La Tangente, j'ai eu l'immense honneur de recevoir Solomon Hykes, le créateur de Docker.Docker a transformé à jamais l'infrastructure et le monde du DevOps. Mais derrière cette révolution se cache une histoire bien plus humaine, pleine de doutes, d'intuition, de paris risqués… et de vision.On revient ensemble sur :la genèse de Docker, née d'une obsession technique à l'écolel'entrée à Y Combinator et la conquête de la Silicon Valleyles moments de doute, les erreurs de management, les leçons tiréespourquoi il a quitté Docker après 10 ansson nouveau projet : Dagger, et l'impact de l'IA sur les pipelines de CI/CDUn épisode sans filtre, passionnant, technique, inspirant – à ne surtout pas manquer.

This week on The Business of Open Source, I have the first episode I recorded on-site at KubeCon Salt Lake City (and the only full-length episode), with Solomon Hykes, CEO and co-founder of Dagger, and co-founder of Docker.One thing Solomon mentions briefly but that is very important is that there are limits to what can be learned from Docker's story, simply because the situation was so unique. Docker experienced explosive growth, at least some of which was due to having the right technology at the right time. This kind of explosive growth is very rare, though, and it brought it's own set of challenges. The point being that while most companies will struggle to get enough adoption, Docker struggled to monetize effectively but got so many chances to try again just because it had a massive community. The hypothesis — or actually, lack thereof — behind creating the original Docker open source project. How having a massive community does help — but also doesn't guarantee you'll be able to build a financially sustainable companyWhen you build a massively successful technology or standard, you'll attract competition — and in the case of Docker, the competitors were savvy companies who'd won the previous cloud wars and ultimately were quicker to figure out how to monetize Docker containers than Docker itselfWhat Solomon is doing differently at Dagger compared to Docker, one of which is thinking about monetization much soonerThe open source movement was founded on such explicitly anti-commercial principles that companies building in the space would often not be intellectually honest about the fact that they were building both a software to give away for free as well as a business that needed revenue. Docker tried too hard to please everyone, including those who felt that open source should be pure and non-commercial — at Dagger, they're much more transparent and upfront about the fact that it's a company with commercial ambitions. Solomon also talked about the difference between components and product, and how designing products requires control, including the ability to just say no without explaining yourself. ###It was fascinating to hear Solomon talk about the lack of intellectual honesty around who pays for the development and maintenance of a lot of open source projects, because that precise topic was the focus of two panels I moderated at KubeCon, one during the main conference and one during CloudNative StartupFest. If you're struggling to articulate how your product and project are different from each other (and others in the ecosystem) and why someone should pay you, you might want to work with me. Reach out! 

“Carlos” … dans le monde de la CIB, son prénom suffit à inspirer le respect.Et c'est la première fois que Carlos Gonçalves se raconte dans un podcast. Rien que ça justifie que vous vous jetiez sur cet épisode exceptionnel.Carlos a démarré tout en bas de l'échelle, tombant un peu par hasard dans le monde de l'IT bancaire dans les années 90 - un moment de tournant technologique majeur.Année après année, il développe son Leadership comme aucune autre personne que je connaisse.Devops, agilité à l'échelle, Crafstmanship, Cloud : il propulse l'IT de la Société Générale au plus haut niveau technologique mondial - avec des années d'avance sur la compétitition.Il s'appuie pour cela sur des partenariats incroyables : avec Jeff Sutherland (pape mondial du Scrum), Werner Voggels pour AWS, Solomon Hykes pour Docker, Scott Guthrie pour Azure

Solomon Hykes is the co-founder of Dagger. He is probably best known as the creator of Docker. The tool that changed how developers package, run and distribute software in the last 11 years. His impact on our industry is undeniable. Today, we discuss his new venture, Dagger. Dagger is a new approach to how we do CI/CD.   Do you have something cool to share? Some questions? Let us know: - web: kubernetespodcast.com - mail: kubernetespodcast@google.com - twitter: @kubernetespod News of the week Kubeadm v1beta4 1.32 Release Cycle Info Updates to the Certified Kubernetes Administrator Exam 2024 Generative AI Survey Microsoft Azure Advanced Container Networking enhancements   Links from the interview Solomon Hykes on LinkedIn Dagger OpenStack Act (GitHub Actions Locally) Buildkit Cue GraphQL Dagger Discord Caching - Dagger Documentation Bazel Terraform Pulumi Kubectl gRPC GraphQL Google Cloud's Package Index The Daggerverse Cloud Foundry PostHog RedHat Development Model Links from the post-interview chat Scaffold Solomon Hykes - Docker, Dagger, and the Future of DevOps Directed Acyclic Graphs Solomon Hykes on wikipedia Stack Overflow  

This week, we discuss Forrester's LLM Wave, Nvidia's Market Cap Dilemma, and why everything is code. Plus, Matt Ray explains more about Australian slang. Watch the YouTube Live Recording of Episode (https://www.youtube.com/watch?v=jfWDSWwjpPM) 472 (https://www.youtube.com/watch?v=jfWDSWwjpPM) Runner-up Titles Is pig latin American? The final boss for Duolingo The Corrections Episode You can always get it from the leader Frito Lay of Chips Everything is code Rundown Forrester has no idea what its talking about (https://www.threads.net/@aakashg0/post/C78Ob6MBYxv) Get it from Google (https://cloud.google.com/resources/forrester-wave-ai-foundation-models?hl=en). Nvidia Nvidia Earnings: Stock Rallies As AI Giant Reports 600% Profit Explosion, 10-For-1 Stock Split (https://www.forbes.com/sites/dereksaul/2024/05/22/nvidia-earnings-stock-rallies-as-ai-giant-reports-600-profit-explosion/?sh=18dffe2e4679) Nvidia: Short bets against stock top $34B (https://finance.yahoo.com/video/nvidia-short-bets-against-stock-143717553.html) Nvidia to Become $10T Company: I/O Fund's Kindig (https://www.bloomberg.com/news/videos/2024-05-23/i-o-fund-s-kindig-nvidia-to-become-10t-company-video) Intel CEO Fires Back at Nvidia in Battle for AI Chip Leadership (https://www.bloomberg.com/news/articles/2024-06-04/intel-ceo-fires-back-at-nvidia-in-battle-for-ai-chip-leadership) Peak Nvidia (https://x.com/netcapgirl/status/1797994922735522260) Solomon Hykes & Dagger (https://www.thecloudcast.net/2024/06/solomon-hykes-dagger.html) Relevant to your Interests Ghost jobs : The Indicator from Planet Money (https://www.npr.org/2024/06/07/1197965117/ghost-jobs) Apple to ‘Pay' OpenAI for ChatGPT Through Distribution, Not Cash (https://www.bloomberg.com/news/articles/2024-06-12/apple-to-pay-openai-for-chatgpt-through-distribution-not-cash) Broadcom soars as demand for AI chips power forecast raise (https://finance.yahoo.com/news/broadcom-soars-demand-ai-chips-121601719.html) Clouded Judgement 6.14.24 - Is Seat Based Pricing Dead? (https://cloudedjudgement.substack.com/p/clouded-judgement-61424-is-seat-based?utm_source=post-email-title&publication_id=56878&post_id=145395123&utm_campaign=email-post-title&isFreemail=true&r=2l9&triedRedirect=true&utm_medium=email) Olivier Pomel (CEO, Datadog) Shares Every Lesson From Scaling to $40B (https://www.theloganbartlettshow.com/archive/ep-108-olivier-pomel-ceo-datadog-shares-every-[…]om-scaling-to-40b?utm_source=substack&utm_medium=email) US sues Adobe for hiding termination fees and making it difficult to cancel subscriptions (https://techcrunch.com/2024/06/17/us-sues-adobe-for-hiding-termination-fees-and-making-it-difficult-to-cancel-subscriptions/) Senior Engineer Fatigue (https://luminousmen.com/post/senior-engineer-fatigue?utm_source=changelog-news) AWS' AI And GenAI Leader Leaves For DigitalOcean As New CTO (https://www.crn.com/news/cloud/2024/aws-ai-and-genai-leader-jumps-to-digitalocean-as-new-cpto) The Framework Laptop 13 is about to become one of the world's first RISC-V laptops (https://www.theverge.com/2024/6/18/24181278/framework-laptop-risc-v-laptop-isa-arm-amd-intel-x86) A Look Back at Q1 '24 Public Cloud Software Earnings (https://open.substack.com/pub/cloudedjudgement/p/a-look-back-at-q1-24-public-cloud?r=2l9&utm_medium=ios) Nonsense You can renew U.S. passports online again (https://www.washingtonpost.com/travel/2024/06/12/passport-renewal-online-travel/) The Excel superstars throw down in Vegas (https://www.theverge.com/c/24133822/microsoft-excel-spreadsheet-competition-chapmionship) Conferences DevOpsDays Amsterdam (https://devopsdays.org/events/2024-amsterdam/welcome/), June 19-21, 2024, Coté speaking. DevOpsDays Birmingham, August 19–21, 2024 (https://devopsdays.org/events/2024-birmingham-al/welcome/) DevOpsDays Antwerp (https://devopsdays.org/events/2024-antwerp/welcome/), 15th anniversary, Sep 4th-5th. SpringOne (https://springone.io/?utm_source=cote&utm_campaign=devrel&utm_medium=newsletter&utm_content=newsletterUpcoming)/VMware Explore US (https://blogs.vmware.com/explore/2024/04/23/want-to-attend-vmware-explore-convince-your-manager-with-these/?utm_source=cote&utm_campaign=devrel&utm_medium=newsletter&utm_content=newsletterUpcoming), August 26–29, 2024 SREday London 2024 (https://sreday.com/2024-london/), September 19th to 20th, Coté speaking. 20% off with the code SRE20DAY (https://sreday.com/2024-london/#tickets) SDT news & hype Join us in Slack (http://www.softwaredefinedtalk.com/slack). Get a SDT Sticker! Send your postal address to stickers@softwaredefinedtalk.com (mailto:stickers@softwaredefinedtalk.com) and we will send you free laptop stickers! Follow us: Twitch (https://www.twitch.tv/sdtpodcast), Twitter (https://twitter.com/softwaredeftalk), Instagram (https://www.instagram.com/softwaredefinedtalk/), Mastodon (https://hachyderm.io/@softwaredefinedtalk), BlueSky (https://bsky.app/profile/softwaredefinedtalk.com), LinkedIn (https://www.linkedin.com/company/software-defined-talk/), TikTok (https://www.tiktok.com/@softwaredefinedtalk), Threads (https://www.threads.net/@softwaredefinedtalk) and YouTube (https://www.youtube.com/channel/UCi3OJPV6h9tp-hbsGBLGsDQ/featured). Use the code SDT to get $20 off Coté's book, Digital WTF (https://leanpub.com/digitalwtf/c/sdt), so $5 total. Become a sponsor of Software Defined Talk (https://www.softwaredefinedtalk.com/ads)! Recommendations Brandon: Houston Public Library (https://houstonlibrary.org/mylink) and Libby (https://libbyapp.com/interview/welcome#doYouHaveACard) Matt: Dissect podcast (https://dissectpodcast.com/) Coté: Ikea RIKLIG (https://www.ikea.com/nl/en/p/riklig-teapot-glass-40297848/) - small, glass teapot. Photo Credits Header (https://unsplash.com/photos/a-small-animal-standing-on-top-of-a-pile-of-rocks-pk8WuEOSPHA) Artwork (https://unsplash.com/photos/close-up-photography-of-green-motherboard--9jmFkN-_U4) Wave (https://www.threads.net/@aakashg0/post/C78Ob6MBYxv)

Solomon Hykes (@solomonstre, Co-Founder @Dagger_io) talks about the evolution of the container industry, fixing broken CI/CD systems, and modern DevOps.SHOW: 829CLOUD NEWS OF THE WEEK - http://bit.ly/cloudcast-cnotwNEW TO CLOUD? CHECK OUT OUR OTHER PODCAST - "CLOUDCAST BASICS"SPONSOR:See what graphs can do for you at Neo4j.com/developerSHOW NOTES:https://dagger.io/InfoQ Article on DaggerDaggar and GPTScript for AI (video)Tech Crunch ArticleSolomon's first time on The Cloudcast - Episode #66Topic 1 - Welcome back to the show. We've spoken a number of times over the years and we've been overdue to catch up. For the few listeners out there who might not be familiar, give everyone a quick intro and your background with Docker and containers prior to Dagger.Topic 2 - Dagger has been around for a few years, coming out of stealth in 2022. If I understand Dagger correctly, it is a declarative model to abstract away CI/CD pipelines. What problem are you trying to solve?Topic 2a - Anytime you add an abstraction layer, you potentially add overhead and complexity. What are your thoughts on this?Topic 3 - Let's go back to containers quickly. How has Containers as an “industry” changed over the years? How does that relate to what you are trying to do with Dagger?Topic 3a - What lessons learned from Docker and even back to dotCloud days do you want to bring forward with Dagger?Topic 4 - What metrics are organizations using to measure the performance and success of Dagger implementations? Is it velocity (number of deployments)? Reduction in friction?Topic 4a - I get the advantage on the Dev side of DevOps, what's in it for Ops?Topic 5 - Dagger has three components, Dagger Engine, Dagger Cloud and Dagger SDK. Walk everyone through the offerings at a high level.FEEDBACK?Email: show at the cloudcast dot netTwitter: @cloudcastpodInstagram: @cloudcastpodTikTok: @cloudcastpod

This week we have Solomon Hykes, the creator of Docker and co founder of Dagger. We talk about the history of Docker and how it has impacted the development community. Then we dive into Dagger and how it's simplifying CI pipelines with code. We also talk about the future of DevOps and AI integration. https://twitter.com/solomonstre https://dagger.io/ Episode sponsored By Clerk (https://clerk.com) Become a paid subscriber our patreon, spotify, or apple podcasts for the full episode. https://www.patreon.com/devtoolsfm https://podcasters.spotify.com/pod/show/devtoolsfm/subscribe https://podcasts.apple.com/us/podcast/devtools-fm/id1566647758 https://www.youtube.com/@devtoolsfm/membership

Intro Mike: Hello and welcome to Open Source Underdogs! I’m your host Mike Schwartz, Founder of Gluu, and this is episode 68 with Solomon Hykes, Co-Founder and CEO of Dagger, but also formerly the co-founder and CTO of Docker. Back in February, I recorded this episode at the Civo Navigate conference in my hometown of Austin,... The post Episode 68: Solomon Hykes, Co-Founder / CEO Dagger first appeared on Open Source Underdogs.

Application delivery doesn't have to suck. Bret and Nirmal are joined by Solomon Hykes, the founder or Docker, to talk about Dagger and their application delivery-as-code that runs anywhere.

In episode 39 of The Kubelist Podcast, Marc and Benjie recount their experience at KubeCon 2023 and share interviews from the event with guests like Matt Butcher and Radu Matei of Fermyon, Umair Khan of Stacklet, Anna Reale of Keptn, Solomon Hykes of Dagger, Bailey Hayes of wasmCloud, and many more.

In episode 39 of The Kubelist Podcast, Marc and Benjie recount their experience at KubeCon 2023 and share interviews from the event with guests like Matt Butcher and Radu Matei of Fermyon, Umair Khan of Stacklet, Anna Reale of Keptn, Solomon Hykes of Dagger, Bailey Hayes of wasmCloud, and many more.

In this episode, Solomon Hykes, founder of Dagger and the original Docker project, sat down with Daniel Bryant to discuss the state of DevOps and how the new open source Dagger project aims to improve continuous delivery practices. Topics covered included the challenges of building applications, modernizing CI/CD tooling and practices, and building an effective community. Read a transcript of this interview: https://bit.ly/3Rv6F6k Subscribe to the Software Architects' Newsletter [monthly]: www.infoq.com/software-architect…mpaign=architectnl Upcoming Events: QCon London https://qconlondon.com/ April 8-10, 2024 Follow InfoQ: - Mastodon: https://techhub.social/@infoq - Twitter: twitter.com/InfoQ - LinkedIn: www.linkedin.com/company/infoq - Facebook: bit.ly/2jmlyG8 - Instagram: @infoqdotcom - Youtube: www.youtube.com/infoq Write for InfoQ - Join a community of experts. - Increase your visibility. - Grow your career. www.infoq.com/write-for-infoq/?u…aign=writeforinfoq

This week we're gleaming the KubeCon. Ok, some people say CubeCon, while others say KubeCon…we talk with Solomon Hykes about all things Dagger, Tammer Saleh and James McShane about going beyond cloud native with SuperOrbital, and Steve Francis and Spencer Smith about the state of Talos Linux and what they're working on at Sidero Labs.

This week we're gleaming the KubeCon. Ok, some people say CubeCon, while others say KubeCon…we talk with Solomon Hykes about all things Dagger, Tammer Saleh and James McShane about going beyond cloud native with SuperOrbital, and Steve Francis and Spencer Smith about the state of Talos Linux and what they're working on at Sidero Labs.

This week we're joined by Solomon Hykes, the creator of Docker. Now he's back with his next big thing called Dagger — CI/CD as code that runs anywhere. We're users of Dagger so check out our codebase if you want to see how it works. On today's show Solomon takes us back to the days of Docker, what it was like on that 10 year journey, his transition from Docker to Dagger, Dagger's community-led growth model, their focus on open source and community, how it works, and even a cameo from Kelsey Hightower to explain how Dagger works.

This week we're joined by Solomon Hykes, the creator of Docker. Now he's back with his next big thing called Dagger — CI/CD as code that runs anywhere. We're users of Dagger so check out our codebase if you want to see how it works. On today's show Solomon takes us back to the days of Docker, what it was like on that 10 year journey, his transition from Docker to Dagger, Dagger's community-led growth model, their focus on open source and community, how it works, and even a cameo from Kelsey Hightower to explain how Dagger works.

Lors du premier KCD France, nous avons eu la chance de pouvoir interviewer Solomon, un monsieur qui compte beaucoup pour nous tous. Car sans lui et sa talentueuse équipe chez Docker, beaucoup ne seraient pas là à pousser du container par monts et par vaux. Aujourd'hui nous ne parlerons pas de Docker (même si...) mais de son dernier bébé très prometteur qui révolutionnera peut-être à nouveau le monde IT et plus précisément celui de la CI/CD. C'est tout le mal que nous lui souhaitons car pour avoir travaillé avec, c'est rafraichissant et assez disruptant. Merci à toi, Solomonstre

In episode 37 of The Kubelist Podcast, Marc and Benjie speak with Solomon Hykes about his new project, Dagger. This talk explores CI/CD in depth and examines the difficulties teams face when implementing it. Finally, Solomon looks back on the lessons he learned while building Docker and how they ultimately influenced the creation and trajectory of Dagger.

In episode 37 of The Kubelist Podcast, Marc and Benjie speak with Solomon Hykes about his new project, Dagger. This talk explores CI/CD in depth and examines the difficulties teams face when implementing it. Finally, Solomon looks back on the lessons he learned while building Docker and how they ultimately influenced the creation and trajectory of Dagger.

In episode 36 of The Kubelist Podcast, Benjie and Marc speak with Solomon Hykes, founder of both Docker and Dagger. This conversation explores the early days of containers and the origins of Docker, including the many hurdles Docker overcame early on, its unexpected virality, and its continued prevalence among the developer community.

In episode 36 of The Kubelist Podcast, Benjie and Marc speak with Solomon Hykes, founder of both Docker and Dagger. This conversation explores the early days of containers and the origins of Docker, including the many hurdles Docker overcame early on, its unexpected virality, and its continued prevalence among the developer community.

Loris Degioanni (@lorisdegio) joins Eric Anderson (@ericmander) to chat about Falco, the open-source runtime security tool for modern cloud infrastructures. Loris is the founder and CTO of Sysdig, and co-creator of Wireshark, the legendary open-source packet analysis tool. Today, Loris talks about all these projects and more - tune in to learn about some deep history and Loris' predictions for the future. Subscribe to Contributor on Substack for email notifications, and join our Slack community! In this episode we discuss: How Loris began working with Gerald Combs as a student in Italy Why Loris' teams name their products after animals The new non-profit Wireshark Foundation Parallel development of cloud technology and containers during Loris' career The little things that make open-source projects go viral Links: Falco Sysdig Wireshark People mentioned: Solomon Hykes (@solomonhykes)

Docker und Container: Buzzwords der letzten Dekade - Doch was ist Docker wirklich?In dieser Episode versuchen wir genau diese Frage zu beantworten. Jeder redet davon, und wie in jedem Hype werden Wörter und Begriffe oft in einem falschen Kontext genutzt und das Ecosystem entwickelt sich unglaublich schnell. Deswegen ist es doch ganz gut, wenn man ein wenig hinter die Kulissen schaut: Warum wurde Docker erschaffen und welches ursprüngliche Problem sollte es lösen? Was ist das besondere an Docker, wenn es "diese Linux Container" bereits seit > 20 Jahren gibt? Was ist eigentlich ein Container im Kontext von Software und was hat "Change Root" (chroot) damit zu tun? Und welche Nachteile hat Docker?Kurz um: 55 Minuten um das “Warum” hinter Docker.Bonus: Warum Duisburg eine essentielle Rolle im Container-Ecosystem spielt, was Kaffe mit Software deployen zu tun hat und wie man das Endstück vom Brot nennt.Feedback (gerne auch als Voice Message)Email: stehtisch@engineeringkiosk.devTwitter: https://twitter.com/EngKioskWhatsApp +49 15678 136776Gerne behandeln wir auch euer Audio Feedback in einer der nächsten Episoden, einfach Audiodatei per Email oder WhatsApp Voice Message an +49 15678 136776Linkslocalhost Konferenz: https://localhost.engineering/Landschaftspark Duisburg-Nord: https://www.landschaftspark.de/Nomad von Hashicorp: https://www.nomadproject.io/Docker auf der pycon 2013: "The future of Linux Containers": https://www.youtube.com/watch?v=wW9CAH9nSLsdotCloud: https://www.docker.com/press-release/dotcloud-inc-now-docker-inc/"Why we built Docker" Solomon Hykes auf der dotScale 2013: https://www.youtube.com/watch?v=3N3n9FzebAA10+ Deploys Per Day: Dev and Ops Cooperation at Flickr: https://www.slideshare.net/jallspaw/10-deploys-per-day-dev-and-ops-cooperation-at-flickrLinux Containers (LXC): https://de.wikipedia.org/wiki/LXClibcontainer: https://github.com/opencontainers/runc/tree/main/libcontainerFROM scratch-Container: https://hub.docker.com/_/scratchContainers are chroot with a Marketing Budget: https://earthly.dev/blog/chroot/Metabase: https://github.com/metabase/metabaseQemu: https://www.qemu.org/Die 100 häufigsten Wörter für das Brotende: https://100woerter.de/100-haeufigsten-woerter-fuer-das-brotende/Der Sprachatlas - Brotende: https://www.atlas-alltagssprache.de/r10-f3h/?child=rundeSprungmarken(00:00:00) Intro(00:00:54) Wolfgangs Weltreise und Duisburg's Binnenhafen, der größte der Welt(00:04:16) Das heutige Thema: Docker - Was ist das? Woher kommt es? Sind Docker und Container dasselbe? Und wie sieht das Container-Ecosystem eigentlich aus(00:08:11) Wie lange gibt es Docker bereits? Und welches Problem löst Docker eigentlich?(00:16:47) Was ist der Unterschied zwischen Virtual Machines (VMs) und Jar's zu Docker Containern?(00:21:41) Wann und Wie entstand die Continuous Integration (CI) / Continuous Delivery (CD) / Continuous Deployment (CD) Bewegung?(00:24:38) Was ist eigentlich ein Container im Sinne der Software?(00:29:32) Change root (chroot)(00:31:20) Was ist denn das Besondere an Docker, wenn es Linux Container bereits vorher gab?(00:39:20) Welche Nachteile hat Docker oder ist Docker wie geschnitten Brot?(00:47:37) Das Killer-Argument von Docker: Updaten von Applikationen(00:51:06) Zukünftige Podcast-Episoden über Docker und das Container-Ecosystem(00:52:25) Outro: Feedback und Shownote-LinksHostsWolfgang Gassler (https://twitter.com/schafele)Andy Grunwald (https://twitter.com/andygrunwald)Feedback (gerne auch als Voice Message)Email: stehtisch@engineeringkiosk.devTwitter: https://twitter.com/EngKioskWhatsApp +49 15678 136776

There's a lot going on in the build, pipeline, CI/CD, supply chain space - so much so that there's all these phrases for the concept. Dagger.io is taking stab (hahahahah...) at builds and pipelines.  In this episode, Alex Willians of The New Stack and Coté talk with Solomon Hykes to answer the question "what is Dagger?" We also discuss platform engineering, the concept of programable pipelines, and how Dagger wants you to think. You can also see the video of the demo Solomon gave before this interview and the interview here. This interview was recorded at VMware Explore 2022.

There's a lot going on in the build, pipeline, CI/CD, supply chain space - so much so that there's all these phrases for the concept. Dagger.io is taking stab (hahahahah...) at builds and pipelines.  In this episode, Alex Willians of The New Stack and Coté talk with Solomon Hykes to answer the question "what is Dagger?" We also discuss platform engineering, the concept of programable pipelines, and how Dagger wants you to think. You can also see the video of the demo Solomon gave before this interview and the interview here. This interview was recorded at VMware Explore 2022.

In this episode, we cover: Aaron talks about starting out as a developer and the early stages of cloud development at RBC (1:05) Aaron discusses transitioning to developer advocacy (12:25) Aaron identifies successes he had in his early days of developer advocacy (20:35) Jason asks what it looks like to assist developers in achieving completion with long term maintenance projects, or “sustainable development” (25:40)  Jason and Aaron discuss what “innersource” is and why it's valuable in an organization (29:29) Aaron answers the question “how do you keep skills and knowledge up to date?” (33:55) Aaron talks about job opportunities at RBC (38:55) Links Referenced: Royal Bank of Canada: https://www.rbcroyalbank.com Opportunities at RBC: https://jobs.rbc.com/ca/en TranscriptAaron: And I guess some PM asked my boss, “So, Aaron doesn't come to our platform status meetings, he doesn't really take tickets, and he doesn't take support rotation. What does Aaron do for the Cloud Platform Team?”Jason: [laugh].Jason: Welcome to Break Things on Purpose, a podcast about reliability, learning, and building better systems. In this episode, we talk with Aaron Clark, Director of Developer Advocacy at the Royal Bank of Canada. We chat with him about his journey from developer to advocate, the power of applying open-source principles within organizations—known as innersource—and his advice to keep learning.Jason: Welcome to the show, Aaron.Aaron: Thanks for having me, Jason. My name is Aaron Clark. I'm a developer advocate for cloud at RBC. That is the Royal Bank of Canada. And I've been at the bank for… well, since February 2010.Jason: So, when you first joined the bank, you were not a developer advocate, though?Aaron: Right. So, I have been in my current role since 2019. I've been part of the cloud program since 2017. Way back in 2010, I joined as a Java developer. So, my background in terms of being a developer is pretty much heavy on Java. Java and Spring Boot, now.I joined working on a bunch of Java applications within one of the many functions areas within the Royal Bank. The bank is gigantic. That's kind of one of the things people sometimes struggle to grasp. It's such a large organization. We're something like 100,000… yeah, 100,000 employees, around 10,000 of that is in technology, so developers, developer adjacent roles like business analysts, and QE, and operations and support, and all of those roles.It's a big organization. And that's one of the interesting things to kind of grapple with when you join the organization. So, I joined in a group called Risk IT. We built solely internal-facing applications. I worked on a bunch of stuff in there.I'm kind of a generalist, where I have interest in all the DevOps things. I set up one of the very first Hudson servers in Risk—well, in the bank, but specifically in Risk—and I admin'ed it on the side because nobody else was doing it and it needed doing. After a few years of doing that and working on a bunch of different projects, I was occasionally just, “We need this project to succeed, to have a good foundation at the start, so Aaron, you're on this project for six months and then you're doing something different.” Which was really interesting. At the same time, I always worry about the problem where if you don't stay on something for very long, you never learn the consequences of the poor decisions you may have made because you don't have to deal with it.Jason: [laugh].Aaron: And that was like the flip side of, I hope I'm making good decisions here. It seemed to be pretty good, people seemed happy with it, but I always worry about that. Like, being in a role for a few years where you build something, and then it's in production, and you're running it and you're dealing with, “Oh, I made this decision that seems like a good idea at the time. Turns out that's a bad idea. Don't do that next time.” You never learned that if you don't stay in a role.When I was overall in Risk IT for four, almost five years, so I would work with a bunch of the teams who maybe stayed on this project, they'd come ask me questions. It's like, I'm not gone gone. I'm just not working on that project for the next few months or whatever. And then I moved into another part of the organization, like, a sister group called Finance IT that runs kind of the—builds and runs the general ledger for the bank. Or at least for a part of capital markets.It gets fuzzy as the organization moves around. And groups combine and disperse and things like that. That group, I actually had some interesting stuff that was when I started working on more things like cloud, looking at cloud, the bank was starting to bring in cloud. So, I was still on the application development side, but I was interested in it. I had been to some conferences like OSCON, and started to hear about and learn about things like Docker, things like Kubernetes, things like Spring Boot, and I was like this is some really neat stuff.I was working on a Spark-based ETL system, on one of the early Hadoop clusters at the bank. So, I've been I'm like, super, super lucky that I got to do a lot of this stuff, work on all of these new things when they were really nascent within the organization. I've also had really supportive leadership. So, like, I was doing—that continuous integration server, that was totally on the side; I got involved in a bunch of reuse ideas of, we have this larger group; we're doing a lot of similar things; let's share some of the libraries and things like that. That was before being any, like, developer advocate or anything like that I was working on these.And I was actually funded for a year to promote and work on reuse activities, basically. And that was—I learned a lot, I made a lot of mistakes that I now, like, inform some of the decisions I make in my current role, but I was doing all of this, and I almost described it as I kind of taxed my existing project because I'm working on this team, but I have this side thing that I have to do. And I might need to take a morning and not work on your project because I have to, like, maintain this build machine for somebody. And I had really supportive leadership. They were great.They recognize the value of these activities, and didn't really argue about the fact that I was taking time away from whatever the budget said I was supposed to be doing, which was really good. So, I started doing that, and I was working in finance as the Cloud Team was starting to go through a revamp—the initial nascent Cloud Team at the bank—and I was doing cloud things from the app dev side, but at the same time within my group, anytime something surprising became broken, somebody had some emergency that they needed somebody to drop in and be clever and solve things, that person became me. And I was running into a lot of distractions in that sense. And it's nice to be the person who gets to work on, “Oh, this thing needs rescuing. Help us, Aaron.”That's fantastic; it feels really good, right, up until you're spending a lot of your time doing it and you can't do the things that you're really interested in. So, I actually decided to move over to the Cloud Team and work on kind of defining how we build applications for the cloud, which was really—it was a really good time. It was a really early time in the bank, so nobody really knew how we were going to build applications, how we were going to put them on the cloud, what does that structure look like? I got to do a lot of reading and research and learning from other people. One of the key things about, like, a really large organization that's a little slow-moving like the bank and is a little bit risk-averse in terms of technology choices, people always act like that's always a bad thing.And sometimes it is because we're sometimes not adopting things that we would really get a lot of benefit out of, but the other side of it is, by the time we get to a lot of these technologies and platforms, a bunch of the sharp edges have kind of been sanded off. Like, the Facebooks and the Twitters of the world, they've adopted it and they've discovered all of these problems and been, like, duct-taping them together. And they've kind of found, “Oh, we need to have actual, like, security built into this system,” or things like that, and they've dealt with it. So, by the time we get to it, some of those issues are just not there anymore. We don't have to deal with them.Which is an underrated positive of being in a more conservative organization around that. So, we were figuring there's a lot of things we could learn from. When we were looking at microservices and, kind of, Spring Boot Spring Cloud, the initial cloud parts that had been brought into the organization were mainly around Cloud Foundry. And we were helping some initial app teams build their applications, which we probably over-engineered some of those applications, in the sense that we were proving out patterns that you didn't desperately need for building those applications. Like, you could have probably just done it with a web app and relational database and it would have been fine.But we were proving out some of the patterns of how do you build something for broader scale with microservices and things like that. We learned a bunch about the complexities of doing that too early, but we also learned a bunch about how to do this so we could teach other application teams. And that's kind of the group that I became part of, where I wasn't a platform operator on the cloud, but I was working with dev teams, building things with dev teams to help them learn how to build stuff for cloud. And this was my first real exposure to that scope and scale of the bank. I'd been in the smaller groups and one of the things that you start to encounter when you start to interact with the larger parts of the bank is just, kind of, how many silos there are, how diverse the tech stacks are in an organization of that size.Like, we have areas that do things with Java, we have areas doing things with .NET Framework, we have areas doing lots of Python, we have areas doing lots of Node, especially as the organization started building more web applications. While you're building things with Angular and using npm for the front-end, so you're building stuff on the back-end with Node as well. Whether that is a good technology choice, a lot of the time you're building with what you have. Even within Java, we'd have teams building with Spring Boot, and lots of groups doing that, but someone else is interested in Google Guice, so they're building—instead of Spring, they're using Google Guice as their dependency injection framework.Or they have a… like, there's the mainframe, right? You have this huge technology stack where lots of people are building Java EE applications still and trying to evolve that from the old grungy days of Java EE to the much nicer modern ways of it. And some of the technology conversations are things like, “Well, you can use this other technology; that's fine, but if you're using that, and we're using something else over here, we can't help each other. When I solve a problem, I can't really help solve it for you as well. You have to solve it for yourself with your framework.”I talked to a team once using Vertex in Java, and I asked them, “Why are you using Vertex?” And they said, “Well, that's what our team knew.” I was like, “That's a good technology choice in the sense that we have to deliver. This is what we know, so this is the thing we know we can succeed with rather than actually learning something new on the job while trying to deliver something.” That's often a recipe for challenges if not outright failure.Jason: Yeah. So, it sounds like that's kind of where you come in; if all these teams are doing very disparate things, right—Aaron: Mm-hm.Jason: That's both good and bad, right? That's the whole point of microservices is independent teams, everyone's decoupled, more velocity. But also, there's huge advantages—especially in an org the size of RBC—to leverage some of the learnings from one team to another, and really, like, start to share these best practices. I'm guessing that's where you come into play now in your current role.Aaron: Yeah. And that's the part where how do we have the flexibility for people to make their own choices while standardizing so we don't have this enormous sprawl, so we can build on things? And this is starting to kind of where I started really getting involved in community stuff and doing developer advocacy. And part of how this actually happened—and this is another one of those cases where I've been very fortunate and I've had great leaders—I was working as part of the Cloud Platform Team, the Special Projects group that I was, a couple of people left; I was the last one left. It's like, “Well, you can't be your own department, so you're part of Cloud Platform.” But I'm not an operator. I don't take a support rotation.And I'm ostensibly building tooling, but I'm mostly doing innersource. This is where the innersource community started to spin up at RBC. I was one of the, kind of, founding members of the innersource community and getting that going. We had built a bunch of libraries for cloud, so those were some of the first projects into innersource where I was maintaining the library for Java and Spring using OIDC. And this is kind of predating Spring Security's native support for OIDC—so Open ID Connect—And I was doing a lot of that, I was supporting app teams who were trying to adopt that library, I was involved in some of the other early developer experience things around, you complain this thing is bad as the developer; why do we have to do this? You get invited to one of the VP's regular weekly meetings to discuss, and now you're busy trying to fix, kind of, parts of the developer experience. I was doing this, and I guess some PM asked my boss, “So, Aaron doesn't come to our platform status meetings, he doesn't really take tickets, and he doesn't take support rotation. What does Aaron do for the Cloud Platform Team?”Jason: [laugh].Aaron: And my boss was like, “Well, Aaron's got a lot of these other things that he's involved with that are really valuable.” One of the other things I was doing at this point was I was hosting the Tech Talk speaking series, which is kind of an internal conference-style talks where we get an expert from within the organization and we try to cross those silos where we find someone who's a machine-learning expert; come and explain how TensorFlow works. Come and explain how Spark works, why it's awesome. And we get those experts to come and do presentations internally for RBC-ers. And I was doing that and doing all of the support work for running that event series with the co-organizers that we had.And at the end of the year, when they were starting up a new initiative to really focus on how do we start promoting cloud adoption rather than just people arrive at the platform and start using it and figure it out for themselves—you can only get so far with that—my boss sits me down. He says. “So, we really like all the things that you've been doing, all of these community things and things like that, so we're going to make that your job now.” And this is how I arrived at there. It's not like I applied to be a developer advocate. I was doing all of these things on the side and all of a sudden, 75% of my time was all of these side projects, and that became my job.So, it's not really the most replicable, like, career path, but it is one of those things where, like, getting involved in stuff is a great way to find a niche that is the things that you're passionate about. So, I changed my title. You can do that in some of our systems as long as your manager approves it, so I changed my title from the very generic ‘Senior Technical Systems Analyst—which, who knows what I actually do when that's my title—and I changed that to ‘Developer Advocate.' And that was when I started doing more research learning about what do actual developer advocates do because I want to be a developer advocate. I want to say I'm a developer advocate.For the longest time in the organization, I'm the only person in the company with that title, which is interesting because then nobody knows what to do with me because I'm not like—am I, like—I'm not a director, I'm not a VP. Like… but I'm not just a regular developer, either. Where—I don't fit in the hierarchy. Which is good because then people stop getting worried about what what are titles and things like that, and they just listen to what I say. So, I do, like, design consultations with dev teams, making sure that they knew what they were doing, or were aware of a bunch of the pitfalls when they started to get onto the cloud.I would build a lot of samples, a lot of docs, do a lot of the community engagement, so going to events internally that we'd have, doing a lot of those kinds of things. A lot of the innersource stuff I was already doing—the speaking series—but now it was my job formally, and it helped me cross a lot of those silos and work very horizontally. That's one of the different parts about my job versus a regular developer, is it's my job to cover anything to do with cloud—that at least, that I find interesting, or that my boss tells me I need to work at—and anything anywhere in the organization that touches. So, a dev team doing something with Kubernetes, I can go and talk to them. If they're building something in capital markets that might be useful, I can say, “Hey, can you share this into innersource so that other people can build on this work as well?”And that was really great because I develop all of these relationships with all of these other groups. And that was, to a degree, what the cloud program needed from me as well at that beginning. I explained that this was now my job to one of my friends. And they're like, “That sounds like the perfect job for you because you are technical, but you're really good with people.” I was like, “Am I? I guess I am now that I've been doing it for this amount of time.”And the other part of it as we've gone on more and more is because I talk to all of these development teams, I am not siloed in, I'm not as tunneled on the specific thing I'm working with, and now I can talk to the platform teams and really represent the application developer perspective. Because I'm not building the platform. And they have their priorities, and they have things that they have to worry about; I don't have to deal with that. My job is to bring the perspective of an application developer. That's my background.I'm not an operator; I don't care about the support rotation, I don't care about a bunch of the niggly things and toil of the platform. It's my job, sometimes, to say, hey, this documentation is well-intentioned. I understand how you arrived at this documentation from the perspective of being the platform team and the things that you prioritize and want to explain to people, but as an application developer, none of the information that I need to build something to run on your platform is presented in a manner that I am able to consume. So, I do, like, that side as well of providing customer feedback to the platform saying, “This thing is hard,” or, “This thing that you are asking the application teams to work on, they don't want to care about that. They shouldn't have to care about this thing.” And that sort of stuff.So, I ended up being this human router are sometimes where platform teams will say, “Do you know anybody who's doing this, who's using this thing?” Or finding one app team and say, “You should talk to that group over there because they are also doing the same thing, or they're struggling with the same thing, and you should collaborate.” Or, “They have solved this problem.” Because I don't know every single programming language we use, I don't know all of the frameworks, but I know who I asked for Python questions, and I will send teams to that person. And part of that, then, as I started doing this community work was actually building community.One of the great successes was, we have a Slack channel called ‘Cloud Adoption.' And that was the place where everybody goes to ask their questions about how do I do this thing to put something on Cloud Foundry, put it on Kubernetes? How do I do this? I don't understand. And that was sometimes my whole day was just going onto that Slack channel, answering questions, and being very helpful and trying to document things, trying to get a feel for what people were doing.It was my whole day, sometimes. It took a while to get used to that was actually, like, a successful day coming from a developer background. I'm used to building things, so I feel like success because I built something I can show you, that I did this today. And then I'd have days where I talked to a bunch of people and I don't have anything I can show you. That was, like, the hard part of taking on this role.But one of the big successes was we built this community where it wasn't just me. Other people who wanted to help people, who were just developers on different dev teams, they'd see me ask questions or answer questions, and they would then know the answers and they'd chime in. And as I started being tasked with more and more other activities, I would then get to go—I'd come back to Slack and see oh, there's a bunch of questions. Oh, it turns out, people are able to help themselves. And that was—like that's success from that standpoint of building community.And now that I've done that a couple times with Tech Talks, with some of the developer experience work, some of the cloud adoption work, I get asked internally how do you build community when we're starting up new communities around things like Site Reliability Engineering. How are we going to do that? So, I get—and that feels weird, but that's one of the things that I have been doing now. And as—like, this is a gigantic role because of all of the scope. I can touch anything with anyone in cloud.One of the scope things with the role, but also with the bank is not only do we have all these tech stacks, but we also have this really, really diverse set of technical acumen, where you have people who are experts already on Kubernetes. They will succeed no matter what I do. They'll figure it out because they're that type of personality, they're going to find all the information. If anything, some of the restrictions that we put in place to manage our environments and secure them because of the risk requirements and compliance requirements of being a regulated bank, those will get in the way. Sometimes I'm explaining why those things are there. Sometimes I'm agreeing with people. “Yeah, it sucks. I don't want to have to do this.”But at the same time, you'll have people who they just want to come in, write their code, go home. They don't want to think about technology other than that. They're not going to go and learn things on their own necessarily. And that's not the end of the world. As strange as that sounds to people who are the personality to be constantly learning and constantly getting into everything and tinkering, like, that's me too, but you still need people to keep the lights on, to do all of the other work as well. And people who are happy just doing that, that's also valuable.Because if I was in that role, I would not be happy. And someone who is happy, like, this is good for the overall organization. But the things that they need to learn, the things they need explained to them, the help they need for success is different. So, that's one of the challenges is figuring out how do you address all of those customers? And sometimes even the answer for those customers is—and this is one of the things about my role—it's like the definition is customer success.If the application you're trying to put on cloud should not go on cloud, it is my job to tell you not to put it on cloud. It is not my job to put you on cloud. I want you to succeed, not just to get there. I can get your thing on the cloud in an afternoon, probably, but if I then walk away and it breaks, like, you don't know what to do. So, a lot of the things around how do we teach people to self-serve, how do we make our internal systems more self-serve, those are kind of the things that I look at now.How do I manage my own time because the scope is so big? It's like, I need to figure out where I'm not moving a thousand things forward an inch, but I'm moving things to their completion. And I am learning to, while not managing people, still delegate and work with the community, work with the broader cloud platform group around how do I let go and help other people do things?Jason: So, you mentioned something in there that I think is really interesting, right, the goal of helping people get to completion, right? And I think that's such an interesting thing because I think as—in that advocacy role, there's often a notion of just, like, I'm going to help you get unstuck and then you can keep going, without a clear idea of where they're ultimately heading. And that kind of ties back into something that you said earlier about starting out as a developer where you build things and you kind of just, like, set it free, [laugh] and you don't think about, you know, that day two, sort of, operations, the maintenance, the ongoing kind of stuff. So, I'm curious, as you've progressed in your career, as you've gotten more wisdom from helping people out, what does that look like when you're helping people get to completion, also with the mindset of this is an application that's going to be running for quite some time. Even in the short term, you know, if it's a short-term thing, but I feel like with the bank, most things probably are somewhat long-lived. How do you balance that out? How do you approach that, helping people get to done but also keeping in mind that they have to—this app has to keep living and it has to be maintained?Aaron: Yeah, a lot of it is—like, the term we use is sustainable development. And part of that is kind of removing friction, trying to get the developers to a point where they can focus on, I guess, the term that's often used in the industry is their inner loop. And it should come as no surprise, the bank often has a lot of processes that are high in friction. There's a lot of open a ticket, wait for things. This is the part that I take my conversations with dev teams, and I ask them, “What are the things that are hard? What are the things you don't like? What are the things you wish you didn't have to do or care about?”And some of this is reading between the lines when you talk to them; it's not so much interviewing them. Like, any kind of requirements gathering, usually, it's not what they say, it's what they talk about that then you look at, oh, this is the problem; how do we unstuck that problem so that people can get to where they need to be going? And this kind of informs some of my feedback to the systems we put in place, the processes we put in place around the platform, some of the tooling we look at. I really, really love the philosophy from Docker and Solomon Hykes around, “Batteries included but removable.” I want developers to have a high baseline as a starting point.And this comes partly from my experience with Cloud Foundry. Cloud Foundry has a really great out-of-the-box dev experience for lots of things where, “I just have a web app. Just run it. It's Nginx; it's some HTML pages; I don't need to know all the details. Just make it go and give me the URL.”And I want more of that for app teams where they have a high baseline of things to work with as a starting point. And kind of every organization ends up building this, where they have—like, Netflix: Netflix OSS or Twitter with Finagle—where they have, “Here's the surrounding pieces that I want to plug in that everybody gets as a starting point. And how do we provide security? How do we provide all of these pieces that are major concerns for an app team, that they have to do, we know they have to do?” Some of these are things that only start coming up when they're on the cloud and trying to provide a lot more of that for app teams so they can focus on the business stuff and only get into the weeds when they need to.Jason: As you're talking about these frameworks that, you know, having this high quality or this high baseline of tools that people can just have, right, equipping them with a nice toolbox, I'm guessing that the innersource stuff that you're working on also helps contribute to that.Aaron: Oh, immensely. And as we've gone on and as we've matured, our innersource organization, a huge part of that is other groups as well, where they're finding things that—we need this. And they'll put—it originally it was, “We built this. We'll put it into innersource.” But what you get with that is something that is very targeted and specific to their group and maybe someone else can use it, but they can't use it without bending it a little bit.And I hate bending software to fit it. That's one of the things—it's a very common thing in the corporate environment where we have our existing processes and rather than adopting the standard approach that some tool uses, we need to take it and then bend it until it fits our existing process because we don't want to change our processes. And that gets hard because you run into weird edge cases where this is doing something strange because we bent it. And it's like, well, that's not its fault at that point. As we've started doing more innersource, a lot more things have really become innersource first, where groups realize we need to solve this together.Let's start working on it together and let's design the API as a group. And API design is really, really hard. And how do we do things with shared libraries or services. And working through that as a group, we're seeing more of that, and more commonly things where, “Well, this is a thing we're going to need. We're going to start it in innersource, we'll get some people to use it and they'll be our beta customers. And we'll inform it without really specifically targeting an application and an app team's needs.”Because they're all going to have specific needs. And that's where the, like, ‘included but removable' part comes in. How do we build things extensibly where we have the general solution and you can plug in your specifics? And we're still—like, this is not an easy problem. We're still solving it, we're still working through it, we're getting better at it.A lot of it's just how can we improve day-over-day, year-over-year, to make some of these things better? Even our, like, continuous integration and delivery pipelines to our to clouds, all of these things are in constant flux and constant evolution. We're supporting multiple languages; we're supporting multiple versions of different languages; we're talking about, hey, we need to get started adopting Java 17. None of our libraries or pipelines do that yet, but we should probably get on that since it's been out for—what—almost a year? And really working on kind of decomposing some of these things where we built it for what we needed at the time, but now it feels a bit rigid. How do we pull out the pieces?One of the big pushes in the organization after the log4j CVE and things like that broad impact on the industry is we need to do a much more thorough job around software supply chain, around knowing what we have, making sure we have scans happening and everything. And that's where, like, the pipeline work comes in. I'm consulting on the pipeline stuff where I provide a lot of customer feedback; we have a team that is working on that all full time. But doing a lot of those things and trying to build for what we need, but not cut ourselves off from the broader industry, as well. Like, my nightmare situation, from a tooling standpoint, is that we restrict things, we make decisions around security, or policy or something like that, and we cut ourselves off from the broader CNCF tooling ecosystem, we can't use any of those tools. It's like, well, now we have to build something ourselves, or—which we're never going to do it as well as the external community. Or we're going to just kind of have bad processes and no one's going to be happy so figuring out all of that.Jason: Yeah. One of the things that you mentioned about staying up to speed and having those standards reminds me of, you know, similar to that previous experience that I had was, basically, I was at an org where we said that we'd like to open-source and we used open-source and that basically meant that we forked things and then made our own weird modifications to it. And that meant, like, now, it wasn't really open-source; it was like this weird, hacked thing that you had to keep maintaining and trying to keep it up to date with the latest stuff. Sounds like you're in a better spot, but I am curious, in terms of keeping up with the latest stuff, how do you do that, right? Because you mentioned that the bank, obviously a bit slower, adopting more established software, but then there's you, right, where you're out there at the forefront and you're trying to gather best practices and new technologies that you can use at the bank, how do you do that as someone that's not building with the latest, greatest stuff? How do you keep that skills and that knowledge up to date?Aaron: I try to do reading, I try to set time aside to read things like The New Stack, listen to podcasts about technologies. It's a really broad industry; there's only so much I can keep up with. This was always one of the conversations going way back where I would have the conversation with my boss around the business proposition for me going to conferences, and explaining, like, what's the cost to acquire knowledge in an organization? And while we can bring in consultants, or we can hire people in, like, when you hire new people in, they bring in their pre-existing experiences. So, if someone comes in and they know Hadoop, they can provide information and ideas around is this a good problem to solve with Hadoop? Maybe, maybe not.I don't want to bet a project on that if I don't know anything about Hadoop or Kubernetes or… like, using something like Tilt or Skaffold with my tooling. That's one of the things I got from going to conferences, and I actually need to set more time aside to watch the videos now that everything's virtual. Like, not having that dedicated week is a problem where I'm just disconnected and I'm not dealing with anything. When you're at work, even if KubeCon's going on or Microsoft Build, I'm still doing my day-to-day, I'm getting Slack messages, and I'm not feeling like I can just ignore people. I should probably block out more time, but part of how I stay up to date with it.It's really doing a lot of that reading and research, doing conversations like this, like, the DX Buzz that we invited you to where… I explained that event—it's adjacent to internal speakers—I explained that as I was had a backlog of videos from conferences I was not watching, and secretly if I make everybody else come to lunch with me to watch these videos, I have to watch the video because I'm hosting the session to discuss it, and now I will at least watch one a month. And that's turned out to be a really successful thing internally within the organization to spread knowledge, to have conversations with people. And the other part I do, especially on the tooling side, is I still build stuff. As much as, like, I don't code nearly as much as I used to, I bring an application developer perspective, but I'm not writing code every day anymore.Which I always said was going to be the thing that would make me miserable. It's not. I still think about it, and when I do get to write code, I'm always looking for how can I improve this setup? How can I use this tool? Can I try it out? Is this better? Is this smoother for me so I'm not worrying about this thing?And then spreading that information more broadly within the developer experience group, our DevOps teams, our platform teams, talking to those teams about the things that they use. Like, we use Argo CD within one group and I haven't touched it much, but I know they've got lots of expertise, so talking to them. “How do you use this? How is this good for me? How do I make this work? How can I use it, too?”Jason: I think it's been an incredible, [laugh] as you've been chatting, there are so many different tools and technologies that you've mentioned having used or being used at the bank. Which is both—it's interesting as a, like, there's so much going on in the bank; how do you manage it all? But it's also super interesting, I think, because it shows that there's a lot of interest in just finding the right solutions and finding the right tools, and not really being super-strongly married to one particular tool or one set way to do things, which I think is pretty cool. We're coming up towards the end of our time here, so I did want to ask you, before we sign off, Aaron, do you have anything that you'd like to plug, anything you want to promote?Aaron: Yeah, the Cloud Program is hiring a ton. There's lots of job openings on all of our platform teams. There's probably job openings on my Cloud Adoption Team. So, if you think the bank sounds interesting—the bank is very stable; that's always one of the nice things—but the bank… the thing about the bank, I originally joined the bank saying, “Oh, I'll be here two years, and I'll get bored and I'll leave,” and now it's been 12 years and I'm still at the bank. Because I mentioned, like, that scope and scale of the organization, there's always something interesting happening somewhere.So, if you're interested in cloud platform stuff, we've got a huge cloud platform. If you're in—like, you want to do machine-learning, we've got an entire organization. It should come as no surprise, we have lots of data at a bank, and there's a whole organization for all sorts of different things with machine-learning, deep learning, data analytics, big data, stuff like that. Like, if you think that's interesting, and even if you're not specifically in Toronto, Canada, you can probably find an interesting role within the organization if that's something that turns your crank.Jason: Awesome. We'll post links to everything that we've mentioned, which is a ton. But go check us out, gremlin.com/podcast is where you can find the show note for this episode, and we'll have links to everything. Aaron, thank you so much for joining us. It's been a pleasure to have you.Aaron: Thanks so much for having me, Jason. I'm so happy that we got to do this.Jason: For links to all the information mentioned, visit our website at gremlin.com/podcast. If you liked this episode, subscribe to the Break Things on Purpose podcast on Spotify, Apple Podcasts, or your favorite podcast platform. Our theme song is called, “Battle of Pogs” by Komiku, and it's available on loyaltyfreakmusic.com.

In this episode we talk about launching Dagger with all four founders: Andrea, Eric, Sam & Solomon. While you may remember Sam & Solomon from episode 23, this time we assembled all four superheroes in this story and went deeper, covering nearly three years of refinements, the launch, as well as the world-class team & community that is coming together to solve the next problem of shipping software. Container images and Kubernetes are great steps in the right direction, but now it's time for the next leap into the future. You can use Dagger to run your CI/CD pipelines locally, without needing to commit and push. You can also use Dagger as a Makefile alternative, which resonates with Gerhard, but go further and your perspective on documentation & automation may start shifting. Gerhard believes that this is the Docker moment of CI/CD.

In this episode we talk about launching Dagger with all four founders: Andrea, Eric, Sam & Solomon. While you may remember Sam & Solomon from episode 23, this time we assembled all four superheroes in this story and went deeper, covering nearly three years of refinements, the launch, as well as the world-class team & community that is coming together to solve the next problem of shipping software. Container images and Kubernetes are great steps in the right direction, but now it's time for the next leap into the future. You can use Dagger to run your CI/CD pipelines locally, without needing to commit and push. You can also use Dagger as a Makefile alternative, which resonates with Gerhard, but go further and your perspective on documentation & automation may start shifting. Gerhard believes that this is the Docker moment of CI/CD.

This week we discuss Dagger's Launch, Employee Tacking and Executive Compensation. Plus, some thoughts on beans and broccoli… Register here to be invited to future Software Defined Meetups (https://docs.google.com/forms/d/1HabWg2nxKf2-qAavMSihlHbACjpr-qVDJFeBTKAJZJQ/edit) Rundown Dagger Introducing Dagger: a new way to create CI/CD pipelines (https://dagger.io/blog/public-launch-announcement) Docker founder Solomon Hykes launches Dagger, a new DevOps startup (https://techcrunch.com/2022/03/30/docker-founder-launches-dagger-a-new-devops-platform/) CUE (https://cuelang.org/) Intel CEO Pat Gelsinger earned $178.6M in 2021 (https://twitter.com/Techmeme/status/1509472069804716034) Goldman Sachs is tracking ID swipes so it can crack down on employees who are breaking its return-to-office rules. Here's what happens to those who don't show up enough. (https://www.businessinsider.com/goldman-sachs-is-tracking-swipes-to-get-people-back-rto-2022-3) Relevant to your Interests On Postgres Container Apps. Behold Smooshing: database meet app platform, app platform meet database. (https://redmonk.com/jgovernor/2022/03/31/on-postgres-container-apps-behold-smooshing-database-meet-app-platform-app-platform-meet-database/) Update on “reader” app distribution (https://developer.apple.com/news/?id=grjqafts) Why Apple Is Preparing to Let You Subscribe to Your iPhone (https://www.bloomberg.com/news/newsletters/2022-04-03/will-i-be-able-to-subscribe-to-my-apple-aapl-iphone-and-pay-monthly-l1jc5o3e) Tinybird adds $37 million to run realtime analytics APIs for you (https://techcrunch.com/2022/04/05/tinybird-adds-37-million-to-run-realtime-analytics-apis-for-you/?tpcc=tcplustwitter&guccounter=1&guce_referrer=aHR0cHM6Ly90LmNvLw&guce_referrer_sig=AQAAAM6DbR0JNAhQ2Rv4GtlcllLuggWg2oYNbvCCwzAQ8XySmAM6W8JsJB5QZFYKELlABHfhkjv-SXS4YetXpmgIp0y1MfitJPfDZEwy3yW172Lvu51o_ReSpNixBd1ugWwg-mdixhwkw4i1WM1j8axSwYiOVI4XQrjGNhcjV4xjRcUS) Skillsoft and Codecademy: Equipping today's workforce with the skills for tomorrow (https://www.skillsoft.com/blog/skillsoft-and-codecademy-equipping-todays-workforce-with-the-skills-for-tomorrow) A guide to pronouncing names of global tech companies (https://restofworld.org/2022/global-tech-company-pronunciation-guide/) Google now requires two staff to sign off each Go change (https://www.theregister.com/2022/04/05/google_go_double_sign_off/) Scaling Kubernetes to Over 4k Nodes and 200k Pods (https://medium.com/paypal-tech/scaling-kubernetes-to-over-4k-nodes-and-200k-pods-29988fad6ed) Grafana Labs announces $240 million Series D round led by GIC and welcomes new investor (https://grafana.com/blog/2022/04/06/grafana-labs-series-d/?mdm=social) Microsoft is integrating its Windows 365 Cloud PCs into Windows 11 (https://www.theverge.com/2022/4/5/23011183/microsoft-windows-365-11-integration-cloud-pcs-features?scrolla=5eb6d68b7fedc32c19ef33b4&stream=top) $120M to build a "checkout" button (https://twitter.com/carnage4life/status/1511420421937065984?s=21&t=RAHpnj-JXcBF2yfYUbjNaA) Google Cloud cross-platform data storage engine, BigLake (https://techcrunch.com/2022/04/05/google-cloud-launches-biglake-a-new-cross-platform-data-storage-engine/) Announcing the next generation of Amazon Honeycode (https://honeycodecommunity.aws/t/announcing-the-next-generation-of-amazon-honeycode/16941) Boeing taps Amazon, Microsoft, Google for cloud mega-deal (https://seekingalpha.com/news/3821095-boeing-taps-amazon-microsoft-google-for-cloud-mega-deal-bloomberg) Facebook owner Meta targets virtual currency market with ‘Zuck Bucks' (https://www.ft.com/content/50fbe9ba-32c8-4caf-a34e-234031019371) The first RISC-V portable computer is now available (https://lunduke.substack.com/p/the-first-risc-v-portable-computer) Stanford engineers invent a solar panel that generates electricity at night (https://interestingengineering.com/stanford-solar-panel-night) Global Unicorn Club (https://twitter.com/Brice2B/status/1511593493206077440) IBM 'misclassified' mainframe sales to enrich executives (https://www.theregister.com/2022/04/07/ibm_securities_lawsuit/?td=rt-3a) Warren Buffett's Berkshire Hathaway disclosed late on Wednesday that it had purchased a stake in computer and printer maker HP Inc worth $4.2bn (https://on.ft.com/3r7tuPQ) Ubuntu 22.04 LTS Ready With Mesa 22.0, Early Intel Arc Graphics Enabled & Amber Added (https://www.phoronix.com/scan.php?page=news_item&px=Ubuntu-22.04-Mesa-22.0) PaaS is back: Why enterprises keep trying to resurrect self-service developer platforms (https://www.techrepublic.com/article/paas-is-back-enterprises-self-service-dev-platforms/) We Don't Talk about PaaS - Coté's Commonplace Book - Issue #59 (https://www.getrevue.co/profile/cote/issues/we-don-t-talk-about-paas-cote-s-commonplace-book-issue-59-970679?via=twitter-card&client=DesktopWeb&element=issue-card) Elon Musk is the new Product Manger of Twitter. (http://Elon> Musk just took a 9.2% stake in Twitter — what may happen next) Twitter plans edit button, says Elon Musk's poll had nothing to do with it (https://arstechnica.com/tech-policy/2022/04/twitter-plans-edit-button-says-elon-musks-poll-had-nothing-to-do-with-it/) Announcing AWS Lambda Function URLs: Built-in HTTPS Endpoints for Single-Function Microservices (https://aws.amazon.com/blogs/aws/announcing-aws-lambda-function-urls-built-in-https-endpoints-for-single-function-microservices/) Why AMD Spent $1.9B for Pensando's DPU Biz (https://www.sdxcentral.com/articles/news/why-amd-spent-1-9b-for-pensandos-dpu-biz/2022/04/) Microsoft Azure vaults into the Arm server era with chips from Ampere (https://www.protocol.com/bulletins/microsoft-azure-arm-chips-ampere) Nonsense I Gave My Goldfish $50,000 to Trade Stocks (https://youtu.be/USKD3vPD6ZA) 300 Drones Formed a QR Code That Rick Rolled Dallas on April Fools' Day (https://www.dallasobserver.com/music/dallas-got-rick-rolled-with-a-giant-qr-code-on-april-fools-day-13716928) Comic Helvetic, an Unholy Combo of Comic Sans and Helvetica (https://kottke.org/22/04/comic-helvetic-comic-sans-and-helvetica) Footage of Jay Leno Hosting Windows 95 Launch Event Surfaces Online (https://www.vice.com/en/article/v7d87a/footage-of-jay-leno-hosting-windows-95-launch-event-surfaces-online) American Airlines Restarts Philadelphia Regional Routes With Landline Buses (https://airlineweekly.com/2022/04/american-airlines-restarts-philadelphia-regional-routes-with-landline-buses/) Listener Feedback Magnificent app which corrects your previous console command (https://github.com/nvbn/thefuck) Unity hiring: Senior Strategic Business Development @ Austin, TX, USA (https://careers.unity.com/position/senior-strategic-business-development/3969930) Brain Gracely wants you to join Solo.io in Tech Marketing. (https://twitter.com/bgracely/status/1511357915411750916?s=20&t=Ahsx4cjGziDZ4JQPYWQI2g) Happy Birthday Day to Matt Ray (https://twitter.com/nikiacosta/status/1508084723859533831?s=21&t=sMrz86c8vkj7Ja3mY_tOcQ). Sponsors Traceroute — The Podcast for digital pioneers: https://origins.dev/ Drata — Put Security and Compliance on Autopilot: https://drata.com/partner/SDT Conferences THAT Conference comes to Texas (https://that.us/events/tx/2022/), May 23-26, 2022 Discount Codes: Everything Ticket ($75 off): SDTFriends75 3 Day Camper Ticket ($50 off): SDTFriends50 Virtual Ticket ($75 off): SDTFriendsON75 DevOps Days Birmingham AL, (https://www.papercall.io/devopsdays-2022-birmingham-al), April 18 & 19th, 2022 Spring Tour Chicago (https://tanzu.vmware.com/developer/springone-tour/2022/chicago/), April 26th to 27th. DevOpsDays Austin 2022 (https://devopsdays.org/events/2022-austin/welcome/), May 4 - 5, 2022 DevOpsDays Chicago 2022: (https://sessionize.com/devopsdays-chicago-2022/), May 10 & 11th, 2022 MongoDB World 2022 (https://www.mongodb.com/world-2022), June 7-9th, 2022 Splunk's ,conf (http://Splunk's> ,conf June 13-16, 2022), June 13-16, 2022 THAT Conference Wisconsin (https://that.us/call-for-counselors/wi/2022/), July 25, 2022 VMware Explore 2022, August 29 – September 1, 2022 (https://www.vmware.com/explore.html?src=so_623a10693ceb7&cid=7012H000001Kb0hQAC) SpringOne Platform (https://springone.io/?utm_source=cote&utm_medium=podcast&utm_content=sdt), SF, December 6–8, 2022. SDT news & hype Join us in Slack (http://www.softwaredefinedtalk.com/slack). Get a SDT Sticker! Send your postal address to stickers@softwaredefinedtalk.com (mailto:stickers@softwaredefinedtalk.com) and we will send you free laptop stickers! Follow us on Twitch (https://www.twitch.tv/sdtpodcast), Twitter (https://twitter.com/softwaredeftalk), Instagram (https://www.instagram.com/softwaredefinedtalk/), LinkedIn (https://www.linkedin.com/company/software-defined-talk/) and YouTube (https://www.youtube.com/channel/UCi3OJPV6h9tp-hbsGBLGsDQ/featured). Use the code SDT to get $20 off Coté's book, (https://leanpub.com/digitalwtf/c/sdt) Digital WTF (https://leanpub.com/digitalwtf/c/sdt), so $5 total. Become a sponsor of Software Defined Talk (https://www.softwaredefinedtalk.com/ads)! Recommendations Coté: Cojonudos Espárragos (https://epulumfood.com/conservas/736-esparragos-cojonudos-de-navarra-1316-gruesos-denominacion-de-origen-protegida-el-navarrico-100-natural-8413239002585.html). Matt: Look at Them Beans - Johnny Cash Murder on the Orient Express (https://amzn.to/3JihaT9) (book, not the movie) Brandon: ****Yasso Bars (https://yasso.com/collections/greek-yogurt-bars) Photo Credits Header (https://unsplash.com/photos/phEaeqe555M) Levels Art (https://unsplash.com/photos/gpiKdZmDQig)

What is Akash? Akash is a peer-to-peer marketplace for cloud computing resources and a deployment platform for modern distributed workloads. The big difference of the big value it provides compared to the incumbent (Amazon Web Services or AWS), it's designed for a very modern developer. So what takes normally 10s of hours on a cloud takes minutes, right? So developers can do more with less. And it is private and permissionless. So there's no signup and incredible user experience that you get permissionless networks. And it's, of course, unstoppable, since that's becoming more and more important, considering what's happening today. And, and in a big value is cost. I mean, costs anywhere from two to three X on a normal lower than the Amazons and Googles to Microsoft's, in some cases, even 10 times slower. So that's an incredible value proposition. Episode Index: 0:00 Welcome 0:53 What is Akash Network? 2:15 Current state of the Network 5:21 Akash Token is Liquid and Network is Alive 6:29 Linux Containers and Developer Tools 10:44 Who runs the containers? 13:32 How can it be 2-3x cheaper than AWS? 18:23 Inflationary Rewards Mechanism 20:17 Equinix is an exclusive data center provider 20:53 Mainnet Launch Upcoming! 23:59 COSMOS, Solana and other Ecosystems 25:03 INFURA and Bison Trails 25:42 Managed Node Hosting 27:01 Parler, Censorship Resistance and Deplatforming 34:55 Big upcoming features 40:01 High Performance Computing 40:58 Amazon Web Services and Open Source 46:50 Solomon Hykes, Brian Fox and Alex Ellis

About ScottScott first typed ‘docker run' in 2013 and hasn't looked back. He's been with Docker since 2014 in a variety of leadership roles and currently serves as CEO. His experience previous to Docker includes Sun Microsystems, Puppet, Netscape, Cisco, and Loudcloud (parent of Opsware). When not fussing with computers he spends time with his three kids fussing with computers.Links: Docker: https://www.docker.com Twitter: https://twitter.com/scottcjohnston TranscriptAnnouncer: Hello, and welcome to Screaming in the Cloud with your host, Chief Cloud Economist at The Duckbill Group, Corey Quinn. This weekly show features conversations with people doing interesting work in the world of cloud, thoughtful commentary on the state of the technical world, and ridiculous titles for which Corey refuses to apologize. This is Screaming in the Cloud.Corey: This episode is sponsored in part by Liquibase. If you're anything like me, you've screwed up the database part of a deployment so severely that you've been banned from touching every anything that remotely sounds like SQL, at at least three different companies. We've mostly got code deployments solved for, but when it comes to databases we basically rely on desperate hope, with a roll back plan of keeping our resumes up to date. It doesn't have to be that way. Meet Liquibase. It is both an open source project and a commercial offering. Liquibase lets you track, modify, and automate database schema changes across almost any database, with guardrails to ensure you'll still have a company left after you deploy the change. No matter where your database lives, Liquibase can help you solve your database deployment issues. Check them out today at liquibase.com. Offer does not apply to Route 53.Corey: This episode is sponsored in part by something new. Cloud Academy is a training platform built on two primary goals. Having the highest quality content in tech and cloud skills, and building a good community the is rich and full of IT and engineering professionals. You wouldn't think those things go together, but sometimes they do. Its both useful for individuals and large enterprises, but here's what makes it new. I don't use that term lightly. Cloud Academy invites you to showcase just how good your AWS skills are. For the next four weeks you'll have a chance to prove yourself. Compete in four unique lab challenges, where they'll be awarding more than $2000 in cash and prizes. I'm not kidding, first place is a thousand bucks. Pre-register for the first challenge now, one that I picked out myself on Amazon SNS image resizing, by visiting cloudacademy.com/corey. C-O-R-E-Y. That's cloudacademy.com/corey. We're gonna have some fun with this one!Corey: Welcome to Screaming in the Cloud. I'm Corey Quinn. Once upon a time, I started my public speaking career as a traveling contract trainer for Puppet; I've talked about this before. And during that time, I encountered someone who worked there as an exec, Scott Johnston, who sat down, talked to me about how I viewed things, and then almost immediately went to go work at Docker instead. Today's promoted episode brings Scott on to the show. Scott, you fled to get away from me, became the CEO of Docker over the past, oh what is it, seven years now. You're still standing there, and I'm not making fun of Docker quite the way that I used to. First, thanks for joining me.Scott: Great to be here, Corey. Thanks for the invitation. I'm not sure I was fleeing you, but we can recover that one at another time.Corey: Oh, absolutely. In that era, one of my first talks that I started giving that anyone really paid any attention to was called, “Heresy in the Church of Docker,” where I listed about 10 to 13 different things that Docker didn't seem to have answers for, like network separation, security, audit logging, et cetera, et cetera. And it was a fun talk that I used to basically learn how to speak publicly without crying before and after the talk. And in time, it wound up aging out as these problems got addressed, but what surprised me at the time was how receptive the Docker community was to the idea of a talk that wound up effectively criticizing something that for, well, a number of them it felt a lot of the time like it wasn't that far from a religion; it was very hype-driven: “Docker, Docker, Docker” was a recurring joke. Docker has changed a lot. The burning question that I think I want to start this off with is that it's 2021; what is Docker? Is it a technology? Is it a company? Is it a religion? Is it a community? What is Docker?Scott: Yes. I mean that sincerely. Often, the first awareness or the first introduction that newcomers have is in fact the community, before they get their hands on the product, before they learn that there's a company behind the product is they have a colleague who is, either through a Zoom or sitting next to them in some places, or in a coffee shop, and says, “Hey, you got to try this thing called Docker.” And they lean over—either virtually or physically—and look at the laptop of their friend who's promoting Docker, and they see a magical experience. And that is the introduction of so many of our community members, having spoken with them and heard their own kind of journeys.And so that leads to like, “Okay, so why the excitement? Why did the friend lean over to the other friend and introduce?” It's because the tools that Docker provides just helps devs get their app built and shipping faster, more securely, with choice, without being tied into any particular runtime, any particular infrastructure. And that combination has proven to be a breakthrough dopamine hit to developers since the very beginning, since 2013, when Docker is open-source.Corey: It feels like originally, the breakthrough of Docker, that people will say, “Oh, containers aren't new. We've had that going back to LPARs on mainframes.” Yes, I'm aware, but suddenly, it became easy to work with and didn't take tremendous effort to get unified environments. It was cynically observed at the time by lots of folks smarter than I am, that the big breakthrough Docker had was how to make my MacBook look a lot more like a Linux server in production. And we talk about breaking down silos between ops and dev, but in many ways, this just meant that the silo became increasingly irrelevant because, “Works on my machine” was no longer a problem.“Well, you better back up your email because your laptop's about to go into production in that case.” Containers made it easier and that was a big deal. It seems, on some level, like there was a foray where Docker the company was moving into the world of, “Okay, now we're going to run a lot of these containers in production for you, et cetera.” It really feels like recently, the company as a whole and the strategy has turned towards getting back to its roots of solving developer problems and positioning itself as a developer tool. Is that a fair characterization?Scott: A hundred percent. That's very intentional, as well. We certainly had good products, and great customers, and we're solving problems for customers on the ops side, I'll call it, but when we stood back—this is around 2019—and said, “Where's the real… joy?” For lack of a better word, “Where's the real joy from a community standpoint, from a product experience standpoint, from a what do we do different and better and more capable than anyone else in the ecosystem?” It was that developer experience. And so the reset that you're referring to in November 2019, was to give us the freedom to go back and just focus the entire company's efforts on the needs of developers without any other distractions from a revenue, customer, channel, so on and so forth.Corey: So, we knew this was going to come up in the conversation, but as of a couple of weeks ago—as of the time of this recording—you announced a somewhat, well, let's say controversial change in how the pricing and licensing works. Now, as of—taking effect at the end of this year—the end of January, rather, of next year—Docker Desktop is free for folks to use for individual use, and that's fine, and for corporate use, Docker Desktop also remains free until you are a large company defined by ten million in revenue a year and/or 250 employees or more. And that was interesting and I don't think I'd seen that type of requirement placed before on what was largely an open-source project that's now a developer tool. I believe there are closed-source aspects of it as well for the desktop experience, but please don't quote me on that; I'm not here to play internet lawyer engineer. But at that point, the internet was predictably upset about this because it is easy to yell about any change that is coming, regardless.I was less interested in that than I am in what the reception has been from your corporate customers because, let's be clear, users are important, community is important, but goodwill will not put food on the table past a certain point. There has to be a way to make a company sustainable, there has to be a recurring revenue model. I realize that you know this, but I'm sure there are people listening to this who are working in development somewhere who are, “Wait, you mean I need to add more value than I cost?” It was a hard revelation for [laugh] me back when I had been in the industry a few years—Scott: [laugh]. Sure.Corey: —and I'm still struggling with that—Scott: Sure.Corey: Some days.Scott: You and me both. [laugh].Corey: So, what has the reaction been from folks who have better channels of communicating with you folks than angry Twitter threads?Scott: Yeah. Create surface area for a discussion, Corey. Let's back up and talk on a couple points that you hit along the way there. One is, “What is Docker Desktop?” Docker Desktop is not just Docker Engine.Docker Desktop is a way in which we take Docker Engine, Compose, Kubernetes, all important tools for developers building modern apps—Docker Build, so on and so forth—and we provide an integrated engineered product that is engineered for the native environments of Mac and Windows, and soon Linux. And so we make it super easy to get the container runtime, Kubernetes stack, the networking, the CLI, Compose, we make it super easy just to get that up and running and configured with smart defaults, secured, hardened, and importantly updated. So, any vulnerabilities patched and so on and so forth. The point is, it's a product that is based on—to your comments—upstream open-source technologies, but it is an engineered commercial product—Docker Desktop is.Corey: Docker Desktop is a fantastic tool; I use it myself. I could make a bunch of snide comments that on Mac, it's basically there to make sure the fans are still working on the laptop, but again, computers are hard. I get that. It's incredibly handy to have a graphical control panel. It turns out that I don't pretend to understand those people, but some folks apparently believe that there are better user interfaces than text and an 80-character-wide terminal window. I don't pretend to get those people, but not everyone has the joy of being a Linux admin for far too long. So, I get it, making it more accessible, making it easy, is absolutely worth using.Scott: That's right.Corey: It's not a hard requirement to run it on a laptop-style environment or developer workstation, but it makes it really convenient.Scott: Before Docker desktop, one had to install a hypervisor, install a Linux VM, install Docker Engine on that Linux VM, bridge between the VM and the local CLI on the native desktop—like, lots of setup and maintenance and tricky stuff that can go wrong. Trust me how many times I stubbed my own toes on putting that together. And so Docker Desktop is designed to take all of that setup nonsense overhead away and just let the developer focus on the app. That's what the product is, and just talking about where it came from, and how it uses these other upstream technologies. Yes, and so we made a move on August 31, as you noted, and the motivation was the following: one is, we started seeing large organizations using Docker Desktop at scale.When I say ‘at scale,' not one or two or ten developers; like, hundreds and thousands of developers. And they were clamoring for capabilities to help them manage those developer environments at scale. Second is, we saw them getting a lot of benefit in terms of productivity, and choice, and security from using Docker Desktop, and so we stood back and said, “Look, for us to scale our business, we're at 10-plus million monthly active developers today. We know there's 45 million developers coming in this decade; how do we keep scaling while giving a free experience, but still making sure we can fund our engineers and deliver features and additional value?” We looked at other projects, Corey.The first thing we did is we looked outside our four walls, said, “How have other projects with free and open-source components navigated these waters?” And so the thresholds that you just mentioned, the 250 employees and the ten million revenue, were actually thresholds that we saw others put in place to draw lines between what is available completely for free and what is available for those users that now need to purchase subscription if they're using it to create value for their organizations. And we're very explicit about that. You could be using Docker for training, you could be using Docker for eval in those large organizations; we're not going to chase you or be looking to you to step up to a subscription. However, if you're using Docker Desktop in those environments, to build applications that run your business or that are creating value for your customers, then purchasing a subscription is a way for us to continue to invest in a product that the ecosystem clearly loves and is getting a lot of value out of. And so, that was again, the premise of this change. So, now to the root of your question is, so what's the reaction? We're very, very pleased. First off, yes, there were some angry voices out there.Corey: Yeah. And I want to be clear, I'm not trivializing people who feel upset.Scott: No.Corey: When you're suddenly using a thing that is free and discovering that, well, now you have to pay money for it, people are not generally going to be happy about that.Scott: No.Corey: When people are viewed themselves as part of the community, of contributing to what they saw as a technical revolution or a scrappy underdog and suddenly they find themselves not being included in some way, shape or form, it's natural to be upset, I don't want to trivialize—Scott: Not at all.Corey: People's warm feelings toward Docker. It was a big part of a lot of folks' personality, for better or worse, [laugh] for a few years in there. But the company needs to be sustainable, so what I'm really interested in is what has that reaction been from folks who are, for better or worse, “Yes, yes, we love Docker, but I don't get to sign $100,000 deals because I just really like the company I'm paying the money to. There has to be business value attached to that.”Scott: That's right. That's right. And to your point, we're not trivializing either the reaction by the community, it was encouraging to see many community members got right away what we're doing, they saw that still, a majority of them can continue using Docker for free under the Docker Personal subscription, and that was also intentional. And you saw on the internet and on Twitter and other social media, you saw them come and support the company's moves. And despite some angry voices in there, there was overwhelmingly positive.So, to your question, though, since August 31, we've been overwhelmed, actually, by the positive response from businesses that use Docker Desktop to build applications and run their businesses. And when I say overwhelmed, we were tracking—because Docker Desktop has a phone-home capability—we had a rough idea of what the baseline usage of Docker Desktops were out there. Well, it turns out, in some cases, there are ten times as many Docker Desktops inside organizations. And the average seems to be settling in around three times to four times as many. And we are already closing business, Corey.In 12 business days, we have companies come through, say, “Yes, our developers use this product. Yes, it's a valuable product. We're happy to talk to a salesperson and give you over to procurement, and here we go.” So, you and I both been around long enough to know, like 12 working days to have a signed agreement with an enterprise agreement is unheard of.Corey: Yeah, but let's be very clear here, on The Duckbill Group's side of things where I do consulting projects, I sell projects to companies that are, “Great, this project will take, I don't know, four to six weeks, whatever it happens to be, and, yeah, you're going to turn a profit on this project in about the first four hours of the engagement.” It is basically push button and you will receive more money in your budget than you had when you started, and that is probably the easiest possible enterprise sale, and it still takes 60 to 90 days most of the time to close deals.Scott: That's right.Corey: Trying to get a procurement deal for software through enterprise procurement processes is one of those things when people say, “Okay, we're going to have a signature in Q3,” you have to clarify what year they're talking about. So, 12 days is unheard of.Scott: [laugh]. Yep. So, we've been very encouraged by that. And I'll just give you a rough numbers: the overall response is ten times our baseline expectations, which is why—maybe unanticipated question, or you going to ask it soon—we came back within two weeks—because we could see this curve hit right away on the 31st of August—we came back and said, “Great.” Now, that we have the confidence that the community and businesses are willing to support us and invest in our sustainability, invest in the sustainable, scalable Docker, we came and we accelerated—pulled forward—items in our roadmap for developers using Docker Desktop, both for Docker Personal, for free in the community, as well as the subscribers.So, things like Docker Desktop for Linux, right? Docker Desktop for Mac, Docker Desktop for Windows has been out there about five years, as I said. We have heard Docker Desktop for Linux rise in demand over those years because if you're managing a large number of developers, you want a consistent environment across all the developers, whether they're using Linux, Mac, or Windows desktops. So, Docker Desktop for Linux will give them that consistency across their entire development environment. That was the number two most requested feature on our public roadmap in the last year, and again, with the positive response, we're now able to confidently invest in that. We're hiring more engineers than planned, we're pulling that forward in the roadmap to show that yes, we are about growing and growing sustainably, and now that the environment and businesses are supporting us, we're happy to double down and create more value.Corey: My big fear when the change was announced was the uncertainty inherent to it. Because if there's one thing that big companies don't like, it's uncertainty because uncertainty equates to risk in their mind. And a lot of other software out there—and yes, Oracle Databases I am looking at you—have a historical track record of, “Okay, great. We have audit rights to inspect your environment, and then when we wind up coming in, we always find that there have been licensing shortfalls,” because people don't know how far things spread internally, as well as, honestly, it's accounting for this stuff in large, complex organizations is a difficult thing. And then there are massive fines at stake, and then there's this whole debate back and forth.Companies view contracts as if every company behaves like that when it comes down to per-seat licensing and the rest. My fear was that that risk avoidance in large companies would have potentially made installing Docker Desktop in their environment suddenly a non-starter across the board, almost to the point of being something that you would discipline employees for, which is not great. And it seems from your response, that has not been a widespread reaction. Yes of course, there's always going to be some weird company somewhere that does draconian things that we don't see, but the fact that you're not sitting here, telling me that you've been taking a beating from this from your enterprise buyers, tells me you're onto something.Scott: I think that's right, Corey. And as you might expect, the folks that don't reach out are silent, and so we don't see folks who don't reach out to us. But because so many have reached out to us so positively, and basically quickly gone right to a conversation with procurement versus any sort of back-and-forth or questions and such, tells us we are on the right track. The other thing, just to be really clear is, we did work on this before the August 31 announcement as well—this being how do we approach licensing and compliance and such—and we found that 80% of organizations, 80% of businesses want to be in compliance, they have a—not just want to be in compliance, but they have a history of being in compliance, regardless of the enforcement mechanism and whatnot. And so that gave us confidence to say, “Hey, we're going to trust our users. We're going to say, ‘grace period ends on January 31.'”But we're not shutting down functionality, we're not sending in legal [laugh] activity, we're not putting any sort of strictures on the product functionality because we have found most people love the product, love what it does for them, and want to see the company continue to innovate and deliver great features. And so okay, you might say, “Well, doesn't that 20% represent opportunity?” Yeah. You know, it does, but it's a big ecosystem. The 80% is giving us a great boost and we're already starting to plow that into new investment. And let's just start there; let's start there and grow from there.This episode is sponsored by our friends at Oracle Cloud. Counting the pennies, but still dreaming of deploying apps instead of "Hello, World" demos? Allow me to introduce you to Oracle's Always Free tier. It provides over 20 free services and infrastructure, networking databases, observability, management, and security.And - let me be clear here - it's actually free. There's no surprise billing until you intentionally and proactively upgrade your account. This means you can provision a virtual machine instance or spin up an autonomous database that manages itself all while gaining the networking load, balancing and storage resources that somehow never quite make it into most free tiers needed to support the application that you want to build.With Always Free you can do things like run small scale applications, or do proof of concept testing without spending a dime. You know that I always like to put asterisks next to the word free. This is actually free. No asterisk. Start now. Visit https://snark.cloud/oci-free that's https://snark.cloud/oci-free.Corey: I also have a hard time imagining that you and your leadership team would be short-sighted enough to say, “Okay, that”—even 20% of companies that are willing to act dishonestly around stuff like that seems awfully high to me, but assuming it's accurate, would tracking down that missing 20% be worth setting fire to the tremendous amount of goodwill that Docker still very much enjoys? I have a hard time picturing any analysis where that's even a question other than something you set up to make fun of.Scott: [laugh]. No, that's exactly right Corey, it wouldn't be worth it which is why again, we came out of the gate with like, we're going to trust our users. They love the community, they love the product, they want to support us—most of them want to support us—and, you know, when you have most, you're never going to get a hundred percent. So, we got most and we're off to a good start, by all accounts. And look, a lot of folks too sometimes will be right in that gray middle where you let them know that they're getting away with something they're like, “All right, you caught me.”We've seen that behavior before. And so, we can see all this activity out there and we can see if folks have a license or compliance or not, and sometimes just a little tap on the shoulder said, “Hey, did you know that you might be paying for that?” We've seen most folks at the time say, “Ah, okay. You caught me. Happy to talk to procurement.”So, this does not have to be heavy-handed as you said, it does not have to put at risk the goodwill of the 80%. And we don't have to get a hundred percent to have a great successful business and continuing successful community.Corey: Yeah. I'll also point out that, by my reading of your terms and conditions and how you've specified this—I mean, this is not something I've asked you about, so this could turn into a really awkward conversation but I'm going to roll with it anyway, it explicitly states that it is and will remain free for personal development.Scott: That is correct.Corey: When you're looking at employees who work at giant companies and have sloppy ‘bring your own device' controls around these things, all right, they have it installed on their work machine because in their spare time, they're building an app somewhere, they're not going to get a nasty gram, and they're not exposing their company to liability by doing that?Scott: That is exactly correct. And moreover, just keep looking at those use cases, if the company is using it for internal training or if the company is using it to evaluate someone else's technology, someone else's software, all those cases are outside the pay-for subscription. And so we believe it's quite generous in allowing of trials and tests and use cases that make it accessible and easy to try, easy to use, and it's just in the case where if you're a large organization and your developers are using it to build applications for your business and for your customers, thus you're getting a lot of value using the product, we're asking you to share that value with us so we can continue to invest in the product.Corey: And I think that's a reasonable expectation. The challenge that Docker seems to have had for a while has been that the interesting breakthrough, revelatory stuff that you folks did was all open-source. It was a technology that was incredibly inspired in a bunch of different ways. I am, I guess, mature enough to admit that my take that, “Oh, Docker is terrible”—which was never actually my take—was a little short-sighted. I'm very good at getting things wrong across the board, and that is no exception.I also said virtualization was a flash in the pan and look how that worked out. I was very anti-cloud, et cetera, et cetera. Times change, people change, and doubling down on being wrong gains you nothing. But the question that was always afterwards what is the monetization strategy? Because it's not something you can give away for free and make it up in volume?Even VC money doesn't quite work like that forever, so there's a—the question is, what is the monetization strategy that doesn't leave people either resenting you because, “Remember that thing that used to be free isn't anymore? Doesn't it suck to be you?” And is still accessible as broadly as you are, given the sheer breadth and diversity of your community? Like I can make bones about the fact that ten million in revenue and 250 employees are either worlds apart, or the wrong numbers, or whatever it is, but it's not going to be some student somewhere sitting someplace where their ramen budget is at risk because they have to spend $5 a month or whatever it is to have this thing. It doesn't apply to them.And this feels like, unorthodox though it certainly is, it's not something to be upset about in any meaningful sense. The people that I think would actually be upset and have standing to be upset about this are the enterprise buyers, and you're hearing from them in what is certainly—because I will hear it if not—that this is something they're happy about. They are thrilled to work with you going forward. And I think it makes sense. Even when I was doing stuff as an independent consultant, before I formalized the creation of The Duckbill Group and started hiring people, my policy was always to not use the free tier of things, even if I fit into them because I would much rather personally be a paying customer, which elevates the, I guess, how well my complaints are received.Because I'm a free user, I'm just another voice on Twitter; albeit a loud one and incredibly sarcastic one at times. But if I'm a paying customer, suddenly the entire tenor of that conversation changes, and I think there's value to that. I've always had the philosophy of you pay for the things you use to make money. And that—again, that is something that's easy for me to say now. Back when I was in crippling debt in my 20s, I assure you, it was not, but I still made the effort for things that I use to make a living.Scott: Yeah.Corey: And I think that philosophy is directionally correct.Scott: No, I appreciate that. There's a lot of good threads in there. Maybe just going way back, Docker stands on the shoulders of giants. There was a lot of work with container tech in the Linux kernel, and you and I were talking before about it goes back to LPAR on IBMs, and you know, BS—Berkeley's—Corey: BSD jails and chroots on Linux. Yeah.Scott: Chroot, right? I mean, Bill Joy, putting chroot in—Corey: And Tupperware parties, I'm sure. Yeah.Scott: Right. And all credit to Solomon Hykes, Docker's founder, who took a lot of good up and coming tech—largely on the ops side and in Linux kernel—took the primitives from Git and combined that with immutable copy-on-write file system and put those three together into a really magical combination that simplified all this complexity of dependency management and portability of images across different systems. And so in some sense, that was the magic of standing on these giant shoulders but seeing how these three different waves of innovation or three different flows of innovation could come together to a great user experience. So, also then moving forward, I wouldn't say they're happy, just to make sure you don't get inbound, angry emails—the enterprise buyers—but they do recognize the value of the product, they think the economics are fair and straight ahead, and to your point about having a commercial relationship versus free or non-existing relationship, they're seeing that, “Oh, okay, now I have insight into the roadmap. Now, I can prioritize my requirements that my devs have been asking for. Now, I can double-down on the secure supply chain issues, which I've been trying to get in front of for years.”So, it gives them an avenue that now, much different than a free user as you observed, it's a commercial relationship where it's two way street versus, “Okay, we're just going to use this free stuff and we don't have much of a say because it's free, and so on and so forth.” So, I think it's been an eye-opener for both the company but also for the businesses. There is a lot of value in a commercial relationship beyond just okay, we're going to invest in new features and new value for developers.Corey: The challenge has always been how do you turn something that is widely beloved, that is effectively an open-source company, into money? There have been a whole bunch of questions about this, and it seems that the consensus that has emerged is that a number of people for a long time mistook open-source for a business model instead of a strategy, and it's very much not. And a lot of companies are attempting to rectify that with weird license changes where, “Oh, you're not allowed to take our code and build a service out of it if you're a cloud provider.” Amazon's product strategy is, of course, “Yes,” so of course, there's always going to be something coming out of AWS that is poorly documented, has a ridiculous name, and purports to do the same thing for way less money, except magically you pay them by the hour. I digress.Scott: No, it's a great surface area, and you're right I completely didn't answer that question. [laugh]. So—Corey: No, it's fair. It's—Scott: Glad you brought it back up.Corey: —a hard problem. It's easy to sit here and say, “Well, what I think they should do”—but all of those solutions fall apart under ten seconds of scrutiny.Scott: Super, super hard problem which, to be fair, we as a team and a community wrestled with for years. But here's where we landed, Corey. The short version is that you can still have lots of great upstream open-source technologies, and you'll have an early adopter community that loves those, use those, gets a lot of progress running fast and far with those, but we've found that the vast majority of the market doesn't want to spend its time cobbling together bits and bytes of open-source tech, and maintaining it, and patching it, and, and, and. And so what we're offering is an engineered product that takes the upstream but then adds a lot of value—we would say—to make it an engineered, easy to use, easy to configure, upgraded, secure, so on and so forth. And the convenience of that versus having to cobble together your own environment from upstream has proved to be what folks are willing to pay for. So, it's the classic kind of paying for time and convenience versus not.And so that is one dimension. And the other dimension, which you already referenced a little bit with AWS is that we have SaaS; we have a SaaS product in Docker Hub, which is providing a hosted registry with quality content that users know is updated not less than every 30 days, that is patched and maintained by us. And so those are examples of, in some sense, consumption [unintelligible 00:27:53]. So, we're using open-source to build this SaaS service, but the service that users receive, they're willing to pay for because they're not having to patch the Mongo upstream, they're not having to roll the image themselves, they're not having to watch the CVEs and scramble when everything comes out. When there's a CVE out in our upstream, our official images are patched no less than 24 hours later and typically within hours.That's an example of a service, but all based on upstream open-source tech that for the vast majority of uses are free. If you're consuming a lot of that, then there's a subscription that kicks in there as well. But we're giving you value in exchange for you having to spend your time, your engineers, managing all that that I just walked through. So, those are the two avenues that we found that are working well, that seem to be a fair trade and fair balance with the community and the rest of the ecosystem.Corey: I think the hardest part for a lot of folks is embracing change. And I have encountered this my entire career where I started off doing large-scale email systems administration, and hey, turns out that's not really a thing anymore. And I used to be deep in the bowels of Postfix, for example. I'm referenced in the SVN history of Postfix, once upon a time, just for helping with documentation and finding weird corner cases because I'm really good at breaking things by accident. And I viewed it as part of my identity.And times have changed and moved on; I don't run Postfix myself for anything anymore. I haven't touched it in years. Docker is still there and it's still something that people are actively using basically everywhere. And there's a sense of ownership and identity for especially early adopters who glom on to it because it is such a better way of doing some things that it is almost incomprehensible that we used to do it any other way. That's transformation.That's something awesome. But people want to pretend that we're still living in that era where technology has not advanced. The miraculous breakthrough in 2013 is today's de rigueur type of environment where this is just, “Oh, yeah. Of course you're using Docker.” If you're not, people look at you somewhat strangely.It's like, “Oh, I'm using serverless.” “Okay, but you can still build that in Docker containers. Why aren't you doing that?” It's like, “Oh, I don't believe in running anything that doesn't make me pay AWS by the second.” So okay, great. People are going to have opinions on this stuff. But time marches on and whatever we wish the industry would do, it's going to make its own decisions and march forward. There's very little any of us can do to change that.Scott: That's right. Look, it was a single container back in 2013, 2014, right? And now what we're seeing—and you kind of went there—is we're separating the implementation of service from the service. So, the service could be implemented with a container, could be a serverless function, could be a hosted XYZ as a service on some cloud, but what developers want to do is—what they're moving towards is, assemble your application based on services regardless of the how. You know, is that how a local container? To your point, you can roll a local serverless function now in an OCI image, and push it to Amazon.Corey: Oh, yeah. It's one of that now 34 ways I found to run containers on AWS.Scott: [laugh]. You can also, in Compose, abstract all that complexity away. Compose could have three services in it. One of those services is a local container, one of those services might be a local serverless function that you're running to test, and one of those services could be a mock to a Database as a Service on a cloud. And so that's where we are.We've gone beyond the single-container Docker run, which is still incredibly powerful but now we're starting to uplevel to applications that consist of multiple services. And where do those services run? Increasingly, developers do not need to care. And we see that as our mission is continue to give that type of power to developers to abstract out the how, extract out the infrastructure so they can just focus on building their app.Corey: Scott, I want to thank you so much for taking the time to speak with me. If people want to learn more—and that could mean finding out your opinions on things, potentially yelling at you about pricing changes, more interestingly, buying licenses for their large companies to run this stuff, and even theoretically, since you alluded to it a few minutes ago, look into working at Docker—where can they find you?Scott: No, thanks, Corey. And thank you for the time to discuss and look back over both years, but also zoom in on the present day. So, www.docker.com; you can find any and all what we just walked through. They're more than happy to yell at me on Twitters at @scottcjohnston, and we have a public roadmap that is in GitHub. I'm not going to put the URL here, but you can find it very easily. So, we love hearing from our community, we love engaging with them, we love going back and forth. And it's a big community; jump in, the waters warm, very welcoming, love to have you.Corey: And we'll of course, but links to that in the [show notes. 00:32:28] Thank you so much for your time. I really do appreciate it.Scott: Thank you, Corey. Right back at you.Corey: Scott Johnston, CEO of Docker. I'm Cloud Economist Corey Quinn and this is Screaming in the Cloud. If you've enjoyed this podcast, please leave a five-star review on your podcast platform of choice, whereas if you've hated this podcast, please leave a five-star review on your podcast platform of choice, along with a comment telling me that Docker isn't interested in at all because here's how to do exactly what Docker does in LPARs on your mainframe until the AWS/400 comes to [unintelligible 00:33:02].Scott: [laugh].Corey: If your AWS bill keeps rising and your blood pressure is doing the same, then you need The Duckbill Group. We help companies fix their AWS bill by making it smaller and less horrifying. The Duckbill Group works for you, not AWS. We tailor recommendations to your business and we get to the point. Visit duckbillgroup.com to get started.Announcer: This has been a HumblePod production. Stay humble.

Kevin Hoffman (@KevinHoffman, CTO at @Cosmonic_com, wasmCloud creator) talks about WebAssembly and wasmCloud, and how this new development paradigm can simplify application development.SHOW: 559CLOUD NEWS OF THE WEEK - http://bit.ly/cloudcast-cnotwCHECK OUT OUR NEW PODCAST - "CLOUDCAST BASICS"SHOW SPONSORS:Datadog Security Solution: Modern Monitoring and SecurityStart investigating security threats before it affects your customers with a free 14 day Datadog trial. Listeners of The Cloudcast will also receive a free Datadog T-shirt.CloudZero - Cloud Cost Intelligence for Engineering TeamsSHOW NOTES:Cosmonic (homepage)Webassembly (homepage)wasmCloud (homepage)Getting started with wasmCloudThe Webassembly stack (vs. containers, VMs)Building a Containerless Future with WebAssemblyFrom Napkin to the Cloud - A Webassembly JourneyProgramming Webassembly with Rust (Kevin Hoffman, new book)Topic 1 - Welcome to the show. Let's start by talking a little bit about your background, and what led you to create wasmCloud. Topic 2 - Let's begin by talking about Webassembly. What is it (a language, a framework??), and what problems does it solve for developers?Topic 3 - Let's talk about wasmCloud. Once you've built something leveraging Webassembly, how does it interact with wasmCloud?Topic 4 - Everything in application development tends to be a progression from something prior. How did Webassembly evolve? Docker's Solomon Hykes said that if wasm+wasi existed 7yrs ago, he never would have created Docker. Topic 5 - Yesterday was WASM Day at Cloud Native Con. What were some of the highlights and focus areas?Topic 6 - What are some of the early uses and usage patterns of Webassembly?Topic 7 - What are some of the ways to get started with Webassembly and wasmCloud?FEEDBACK?Email: show at the cloudcast dot netTwitter: @thecloudcastnet

In today's episode, Gerhard is talking to Sam Alba, Docker's first employee, and Solomon Hykes, the Docker co-founder. Together with Andrea Luzzardi, they are the creators of Dagger, a universal deployment engine that trades YAML for CUE, and uses Buildkit as the runtime. Why? Because we should stop rewriting the same application deployment logic in scripts, makefiles or continuous delivery configuration. That's right, this is the YAML vaccine that we have all been waiting for. Gerhard believes that one day, Dagger will become just as meaningful for application delivery, as Docker is today for application code.

In today's episode, Gerhard is talking to Sam Alba, Docker's first employee, and Solomon Hykes, the Docker co-founder. Together with Andrea Luzzardi, they are the creators of Dagger, a universal deployment engine that trades YAML for CUE, and uses Buildkit as the runtime. Why? Because we should stop rewriting the same application deployment logic in scripts, makefiles or continuous delivery configuration. That's right, this is the YAML vaccine that we have all been waiting for. Gerhard believes that one day, Dagger will become just as meaningful for application delivery, as Docker is today for application code.

The docker project evolved out of the PaaS movement, unlocking polyglot cloud-native applications. But it was only a piece of the puzzle to enable platforms, applications and a broader ecosystem. What lessons can be learned from the docker ecosystem?SHOW: 505SHOW SPONSORS:See how O’Reilly online learning can help your tech teams. Request a free demo now.Zesty Homepage - Real Time Cloud SavingsFree cloud cost-savings evaluation from ZestyCLOUD NEWS OF THE WEEK - http://bit.ly/cloudcast-cnotwCHECK OUT OUR NEW PODCAST - "CLOUDCAST BASICS"SHOW NOTES:Solomon Hykes shows “docker” at PyCon for 1st time (2013)Solomon Hykes on Eps.97, introducing “Docker” (2013)History of Docker, Inc (Wikipedia)dotCloud becomes Docker (2013)Ben Golub (Docker CEO) on Eps.143Diverging Container Standard (Kelsey Hightower, OCI, etc.) - 2016Introducing Kubernetes Container Runtime Interface (CRI) - 2016Microsoft rumored to be buying Docker for $4B (2016)Moby Project announced (2017)Docker Networking with Socketplane (pre-acquisition by Docker)Architectural Considerations for OSS PaaS and Container Platforms (2016) HOW DID docker/DOCKER EVOLVE?Between 2008 and 2013, dozens of PaaS platforms emerged. Within the platform, they all had a model for allocating compute resources, mostly through the use of Linux LXC and cGroups -- what would become containers. dotCloud was the PaaS company started by Solomon Hykes that eventually became Docker. LESSONS LEARNED FOR THE FUTUREContainers were a fundamental building block for next-gen applications and platforms.Docker/docker created a massive community of users, but frustrated the ecosystem of partners. Project / Company naming conflicts are very hard to resolve (“docker” vs. “Docker”)Successful ecosystems allow a broad set of participants to monetize different elements of the technology. Not having a monetization model is not a good plan. Docker was the last software company to not monetize through offering a managed/SaaS cloud service. FEEDBACK?Email: show at thecloudcast dot netTwitter: @thecloudcastnet

This week we discuss a potential Box/Dropbox merger, Discord rumors and the meaning of work. Plus, what happens when you spill water on your laptop? Rundown Could Box and Dropbox Merge? @themotleyfool #stocks $BOX $DBX $MSFT (https://www.fool.com/investing/2021/03/28/could-box-and-dropbox-merge/) Prof. Galloway likes MSFT buying Discord (https://twitter.com/pivotpod/status/1375824932785909760?s=21) Amazon Twitter War (https://twitter.com/delrey/status/1376278015680843779?s=21) Work / Life Tech Support: How can I cope with my meaningless job, and maddening manager? (https://techworker.com/2021/03/29/tech-support-how-can-i-cope-with-my-meaningless-job-and-maddening-manager/) Solomon Hykes is back (https://twitter.com/solomonstre/status/1376725608747593731) McKinsey’s advice to European banks (https://twitter.com/cote/status/1377487540102569984): don’t bring an entourage to meetings. Relevant to your interests IBM doubles down on OpenShift (https://www.protocol.com/newsletters/protocol-enterprise/ibm-red-hat-openshift?rebelltitem=1#rebelltitem1) VMware Cloud announcement (https://twitter.com/VMware/status/1377277520102428679) The New York Times x NFT | Foundation (https://foundation.app/kevinroose/the-new-york-times-x-nft-13129) Software vendors would have to disclose breaches to U.S. government users under new order: draft (https://www.reuters.com/article/idUSL1N2LN3E) Factorio Is The Best Technical Interview We Have (https://erikmcclure.com/blog/factorio-is-best-interview-we-have/) Fintech comes to America at last (https://www.economist.com/leaders/2021/03/27/fintech-comes-to-america-at-last) Buffer overruns, license violations, and bad code: FreeBSD 13’s close call (https://arstechnica.com/gadgets/2021/03/buffer-overruns-license-violations-and-bad-code-freebsd-13s-close-call/) PHP's Git server hacked to add backdoors to PHP source code (https://www.bleepingcomputer.com/news/security/phps-git-server-hacked-to-add-backdoors-to-php-source-code/) T-Mobile is the first US carrier to make Google Messages its default SMS app (https://www.engadget.com/t-mobile-google-messages-212527575.html) Unsplash is being acquired by Getty Images (https://unsplash.com/blog/unsplash-getty/) Introducing the Echo subsea cable (https://cloud.google.com/blog/products/infrastructure/introducing-the-echo-subsea-cable/) LinkedIn confirms it’s working on a Clubhouse rival, too (https://techcrunch.com/2021/03/30/linkedin-confirms-its-working-on-a-clubhouse-rival-too/?guccounter=1&guce_referrer=aHR0cHM6Ly93d3cuaW5vcmVhZGVyLmNvbS8&guce_referrer_sig=AQAAAJNB71cjWYjYTRsUHIQfk7c1dJLL2Af1wKSJBWK5a5-oUxWNhPIQhCbfmqU_X2Sd3O7EVZ3WH2Yi3mc7eYWOqiPRHgAaoSPagsMJO9F3bWeJ-R-D7GgqJvetSKUwaLEC385YjSNeGFM9fjCmCahqjz-xW7juccwvSvMpRZ17lcmf) SSRF vulnerability in NPM package Netmask impacts up to 279k projects (https://portswigger.net/daily-swig/amp/ssrf-vulnerability-in-npm-package-netmask-impacts-up-to-279k-projects) Whistleblower: Ubiquiti Breach “Catastrophic” (https://krebsonsecurity.com/2021/03/whistleblower-ubiquiti-breach-catastrophic/) Ubiquiti, Inc. Investigated for Possible Securities Laws Violations by Block & Leviton LLP; Investors Should Contact the Firm (https://finance.yahoo.com/news/shareholder-alert-ubiquiti-inc-investigated-184800904.html?guccounter=1&guce_referrer=aHR0cHM6Ly9rcmVic29uc2VjdXJpdHkuY29tLzIwMjEvMDMvd2hpc3RsZWJsb3dlci11YmlxdWl0aS1icmVhY2gtY2F0YXN0cm9waGljLw&guce_referrer_sig=AQAAANxzrnuYLGOPmunKjgVOWxc_KbH4rGobv0StOq5Ze80l5-XyX9O12gngluP6MBoSxz0XxAOvkoszFURecya8TaMSVyk6XkgfegqaLR3LnlQvGBTus1iBuuh8FelG1--Pc1u9IGHFs2mlu61HKGw3FRNwhs6qAK9dFslKLAjygggd) ARM introduces v9, its first new chip architecture in a decade (https://www.engadget.com/arm-armv9-architecture-180043435.html) Facebook's new hookup: A pair of submarine cables to link North America, Indonesia, Singapore (https://www.theregister.com/2021/03/30/facebook_new_submarine_cables/) Google is accelerating partial reopening of offices and putting limits on future of remote work (https://www.cnbc.com/2021/03/31/google-speeds-partial-office-reopening-and-puts-limits-on-remote-work.html) Discord’s new Clubhouse-like feature, Stage Channels, is available now (https://www.theverge.com/2021/3/31/22356682/discord-stage-channels-clubhouse-like-feature-voice?scrolla=5eb6d68b7fedc32c19ef33b4) Common Room, Community Management Startup Used By Confluent, Figma And Notion, Launches With $52 Million In Funding (https://www.forbes.com/sites/alexkonrad/2021/03/31/common-room-launches-community-software-with-52-million-funding/) Send AWS Metrics to Partners and to Your Apps in Real Time (https://aws.amazon.com/blogs/aws/cloudwatch-metric-streams-send-aws-metrics-to-partners-and-to-your-apps-in-real-time/) GCP Outpaces Azure, AWS in the 2021 Cloud Report (https://www.cockroachlabs.com/blog/2021-cloud-report/) Slack wants to be more than a text-based messaging platform (https://techcrunch.com/2021/03/26/slack-wants-to-be-more-than-a-text-based-messaging-platform/) Substack raising $65 million in venture capital amid newsletter boom (https://www.axios.com/substack-andreessen-horowitz-newsletter-36cb98ea-a7b3-43b1-883a-fa45586eaad4.html?utm_source=newsletter&utm_medium=email&utm_campaign=newsletter_axiosprorata&stream=top) Nonsense 'Worst mice plague I've ever seen': Millions of rodents descend on eastern Australia (https://www.nbcnews.com/science/science-news/worst-mice-plague-ever-seen-millions-rodents-descend-eastern-australia-rcna513) Silicon Valley Season 2 - Jared Dunn explains what is SWOT Analysis to the team (https://youtu.be/XfB0g_JDIds) Burritos Or Bitcoin: Chipotle To Give Away $200k In Free Burritos And Bitcoin To Celebrate National Burrito Day (https://newsroom.chipotle.com/2021-03-30-Burritos-Or-Bitcoin-Chipotle-To-Give-Away-200k-In-Free-Burritos-And-Bitcoin-To-Celebrate-National-Burrito-Day) Steer through the Suez Canal (https://technologyreview.us11.list-manage.com/track/click?u=47c1a9cec9749a8f8cbc83e78&id=4fd9ae043e&e=84061c219a) Sponsors strongDM — Manage and audit remote access to infrastructure. Start your free 14-day trial today at: strongdm.com/SDT (http://strongdm.com/SDT) CBT Nuggest — Training available for IT Pros anytime, anywhere. Start learning today at cbtnuggets.com/sdt (http://cbtnuggets.com/sdt) Listener Feedback Dominic recommends NewsBlur (https://newsblur.com) to read newsletters Owen recommends Ioreader (https://www.inoreader.com) for newsletters Brian Gracely wants you to work on OpenShift at Red Hat. They are hiring over 10 Product Managers (https://careers-redhat.icims.com/jobs/search?ss=1&searchKeyword=83669). Conferences SpringOne.io (https://springone.io), Sep 1st to 2nd - CFP is open until April 9th (https://springone.io/cfp). Two SpringOne Tours: (1.) developer-bonanza in for NA, March 10th and 11th (https://tanzu.vmware.com/developer/tv/springone-tour/0014/), and, (2.) EMEA dev-fest on April 28th (https://tanzu.vmware.com/developer/tv/springone-tour/0015/). VMware Tanzu Up Close Virtual Event (https://connect.tanzu.vmware.com/EMEA_P5_FE_Q122_Event_VMware-Tanzu-Up-Close.html), April 27, 2021, 10:00am - 5:50pm CET SDT news & hype Join us in Slack (http://www.softwaredefinedtalk.com/slack). Send your postal address to stickers@softwaredefinedtalk.com (mailto:stickers@softwaredefinedtalk.com) and we will send you free laptop stickers! Follow us on Twitch (https://www.twitch.tv/sdtpodcast), Twitter (https://twitter.com/softwaredeftalk), Instagram (https://www.instagram.com/softwaredefinedtalk/) and LinkedIn (https://www.linkedin.com/company/software-defined-talk/). Brandon built the Quick Concall iPhone App (https://itunes.apple.com/us/app/quick-concall/id1399948033?mt=8) and he wants you to buy it for $0.99. Use the code SDT to get $20 off Coté’s book, (https://leanpub.com/digitalwtf/c/sdt) Digital WTF (https://leanpub.com/digitalwtf/c/sdt), so $5 total. Become a sponsor of Software Defined Talk (https://www.softwaredefinedtalk.com/ads)! Recommendations Matt: GGloba International Power Board Strip (https://www.amazon.com.au/gp/product/B08KLX9H5S/). Brandon: Flame King Propane Torch Weed Burner (https://www.amazon.com/gp/product/B07L5GMWGK/ref=ppx_yo_dt_b_asin_title_o01_s00?ie=UTF8&psc=1). Coté: Brennenstuhl travel plug / travel adapter (travel socket adapter for: Schuko socket and USA & Japan plug) black (https://www.amazon.de/-/en/gp/product/B000WKG5YS/ref=ppx_yo_dt_b_asin_title_o05_s00?ie=UTF8&psc=1). Photo Credit (https://unsplash.com/photos/Of-NXuECJbE) Photo Credit (https://unsplash.com/photos/QL0FAxaq2z0)

In this episode we talk to Greg Osuri, the CEO of Akash Network. The DeCloud for DeFi, and the world's first decentralized cloud computing marketplace built with the help of Cosmos-SDK and Tendermint. Akash Decentralized Cloud is 'a faster, better, and lower cost cloud built for DeFi, decentralized projects, and high growth companies, providing unprecedented scale, flexibility, and price performance. 10x lower in cost, its serverless computing platform is compatible with all cloud providers and all applications that run on the cloud'. We spoke to Greg about decentralized cloud, of course and what are its benefits. About open-source and its efficiency. The stages in the development of cloud technology. Interoperability, scalability, composability... and a lot of other fancy, tech terms that Greg breaks down for much easier understanding. We talked about DeFi and flash loans. About SLA for AWS and alternative data providers. ‘Amazon tax’ and the ‘Burgers and fries’ business model. Gregs's Twitter (https://twitter.com/gregosuri) The projects and people that have been mentioned in this episode: | Tendermint (https://tendermint.com/) | Cosmos (https://cosmos.network/) | Akash Network (https://akash.network/) | Elastic search (https://www.elastic.co/elasticsearch/) | Filecoin (https://filecoin.io/) | Uniswap (https://uniswap.org/) | MyEtherWallet (https://www.myetherwallet.com/) | Equinix (https://www.equinix.co.uk/) | Nucypher (https://www.nucypher.com/) | Urbit (https://urbit.org/) | Angelhack (https://angelhack.com/) | Kubernetes (https://kubernetes.io/) | IBC (https://cosmos.network/ibc) | Solana (https://solana.com/) | Brian Fox (https://twitter.com/brianjfox) | Solomon Hykes (https://twitter.com/solomonstre) | If you like what we do at Citizen Cosmos: - Stake with Citizen Cosmos validator (https://www.citizencosmos.space/staking) - Help support the project via Gitcoin Grants (https://gitcoin.co/grants/1113/citizen-cosmos-podcast) - Listen to the YouTube version (https://www.youtube.com/watch?v=f3tZLp2CNgI) - Read our blog (https://citizen-cosmos.github.io/blog/) - Check out our GitHub (https://github.com/citizen-cosmos/Citizen-Cosmos) - Join our Telegram (https://t.me/citizen_cosmos) - Follow us on Twitter (https://twitter.com/cosmos_voice) - Sign up to the RSS feed (https://www.citizencosmos.space/rss)

C'est quoi un conteneur et pourquoi les utiliser ?

S01 E07 : Why I love Trunk Based Development (or pushing straight to master) Conducido por @domix y @_marKox 17-Agosto-2019 Revisión de las noticias OpenTracing + OpenCensus = OpenTelemetry (https://www.cncf.io/blog/2019/05/21/a-brief-history-of-opentelemetry-so-far/) OPA Gatekeeper: Policy and Governance for Kubernetes (https://kubernetes.io/blog/2019/08/06/opa-gatekeeper-policy-and-governance-for-kubernetes/) Propuesta de “Archivado” de rkt (https://twitter.com/cra/status/1157443989961789440) Archivado de rkt (https://twitter.com/CloudNativeFdn/status/1162378736194465793) How Google Cloud Storage processes cloud functions 4x faster than Amazon Web Services (https://research.lightstep.com/reports/google-cloud-storage) Serverless gRPC + ASP.NET Core with Knative (https://medium.com/google-cloud/serverless-grpc-asp-net-core-with-knative-b37ce09ea067) Twitter! Solomon Hykes cuestiona las contribuciones de RedHat (https://twitter.com/solomonstre/status/1158535929352638464) Release v0.8 de Knative (https://twitter.com/mchmarny/status/1158794904249569281) Referencias y Recursos How SREs Can Avoid Configuration Drift (https://thenewstack.io/how-enforced-configuration-and-ad-hoc-task-automation-boost-agility/) Introduction to Service Meshes on Kubernetes and Progressive Delivery (https://www.weave.works/blog/introduction-to-service-meshes-on-kubernetes-and-progressive-delivery) Repos chingones de código Awesome Micronaut (https://github.com/JonasHavers/awesome-micronaut) BotKube (https://github.com/infracloudio/botkube) rget - download URLs and verify the contents against a publicly recorded cryptographic log (https://github.com/merklecounty/rget) Eventos Service Mesh Interface Specification Overview and Examples (https://www.meetup.com/San-Diego-Kubernetes-Meetup/events/263943775/) Running Nodeless K8s & Getting Involved in K8s Releases (https://www.meetup.com/Los-Angeles-Kubernetes-Meetup/events/263300724/) Tema del día Why I love Trunk Based Development (or pushing straight to master) (https://medium.com/@mattia.battiston/why-i-love-trunk-based-development-641fcf0b94a0)

Produced by Foundersuite.com, "How I Raised It" goes behind the scenes with startup founders who have raised capital. This episode is with Andrei Serban of Fuzzbuzz.io, a security platform that helps protect software from digital hacks or attacks. The Company raised $2.7 million of seed funding in a deal led by FUEL Capital with participation from Homebrew, Susa Ventures, Solomon Hykes, Florian Leibert and Ben Porterfield. Fuzzbuzz also went through Y Combinator. This series is produced by Foundersuite, makers of software to raise capital and manage investor relations. Foundersuite users have raised over $1.2 Billion since 2016. Learn more at www.foundersuite.com.

On this week's episode, Chris is joined by Lin Clark and Till Schneidereit of Mozilla to discuss all things WebAssembly. Lin and Till are helping to lead the development and advocacy around WebAssembly and in this conversation they discuss the current state of WASM, new developments like the WebAssembly System Interface (WASI), and the longer term possibilities and goals for WASM. Lin Clark Till Schneidereit Code Cartoons WebAssembly Rust TC39 JavaScript committee W3C WebAssembly WebIDL Rust wasm toolchain Babel Emscripten Asm.js Figma WASI Web Assembly System Interface wasmtime Fastly CDN Lucet - Fastly's WASM Runtime Solomon Hykes tweet re: Docker & WASM+WASI The Birth & Death of JavaScript Lin's post on Post MVP future for WASM Mozilla hacks blog WebAssembly's Post MVP Future talk by Lin Clark and Till Schneidereit

French startup Agricool is raising another $28 million round of funding (€25 million). The company is working on containers to grow fruits and vegetables in urban areas, starting with strawberries. Bpifrance, Danone Manifesto Ventures, Marbeuf Capital, Solomon Hykes and other business angels participated in today's funding round. Some existing investors also participated, such as daphni, XAnge, Henri Seydoux and Kima Ventures.

Dans ce nouvel épisode, je vais à la rencontre de Stéphane Reverdy, Senior Product Designer chez Hull. On parle de son parcours entre startups et freelance, de ses challenges aux US et de son retour précipité en France, de sa passion pour l'iconographie et de son travail notamment sur la première icône de l'app iOS d'Airbnb. De sa vision du branding, et du travail en tant que designer en général. Et on termine par la photographie, une passion commune... Belle écoute ! ★★★★★ Si le podcast vous plaît, svp n'oubliez pas d'ajouter 5 étoiles sur iTunes en cliquant ici. Cela me permet de le faire découvrir à d'autres personnes. ✌️

Brian talks with Kendrick “Kenny” Coleman (@kendrickcoleman) about DockerCon 2018 - the announcements, the overall vibe of the event, and how the community is evolving around the event. Show Links: Docker Announcement - Federated Application Management Docker Announcement - Kubernetes on Windows Server Kenny's Podcast - Bourbon Pursuit [PODCAST] @PodCTL - Containers | Kubernetes | OpenShift - RSS Feed, iTunes, Google Play, Stitcher, TuneIn and all your favorite podcast players [A CLOUD GURU] Get The Cloudcast Alexa Skill [A CLOUD GURU] A Cloud Guru Membership - Start your free trial. Unlimited access to the best cloud training and new series to keep you up-to-date on all things AWS. [A CLOUD GURU] FREE access to AWS Certification Exam Prep Guide - At A Cloud Guru, the #1 question received from students is "I want to pass the AWS cert exam, so where do I start?" This course is your answer. [FREE] eBook from O'Reilly Show Notes Topic 1 - Welcome back to the show. First off, before we get into DockerCon, give us an update on Bourbon Pursuit. Topic 2 - Many years ago, when you first came on the show, you were attending one of the first Cloud Foundry Summits, so I guess you’re sort of becoming one of our official Cloudcast event correspondents. Give us an overview of DockerCon 2018 in San Francisco. Topic 3 - Last year (in the US) it was all about “Moby”. Then in Europe it was beginning to be about Kubernetes. This year it seemed to be, as Darren Sheppard (@ibuildthecloud, Rancher CTO) put it “an enterprise sales pitch”. Obviously a lot has changed with Ben Golub and Solomon Hykes leaving Docker. Topic 4 - What were some of the technologies or talks that interested you this week? Topic 5 - Docker has always tried to be the “Apple” of containers - focused on simplicity, clean design. Did you hear any feedback from attendees about how they are accepting the shift to Kubernetes, or other changes they are making? Feedback? Email: show at thecloudcast dot net Twitter: @thecloudcastnet and @ServerlessCast

Mandy Waite joins Mark and Melanie to share what is developer relations and how trust and empathy are key to its success. We discuss meeting developers where they are and the wide variety of differing communities that exist across the technology ecosystem. Mandy Waite Mandy Waite has worked at Google for nearly 8 years, 6 of which have been spent growing and nurturing the Cloud Advocacy team. She heads up the Infrastructure and Ops Advocacy team in Google Cloud with a focus on Cloud Native, DevOps, SRE, Observability and Security. Cool things of the week Better cost control with Google Cloud Billing programmatic notifications blog Music in Motion: a Firebase and IoT story blog Google Cloud Codelabs and Challenges codelabs Kubernetes Podcast site and blog Interview Google Cloud Platform site #46 Borg and K8s with John Wilkes podcast #118 OpenCensus with Morgan McLean and JBD podcast Felipe Hoffa & BigQuery reddit, blog and podcast Livestreaming with Jen Tong Twitch, Holden Karau Twitch, and Chris Broadfoot Twitch Ben Treynor on What is ‘Site Reliability Engineering’ interview Solomon Hykes at dotScale on Docker video Istio site and #85 Istio with Varun Talwar and Sven Mawson podcast Kubernetes site Docker site The Core Competencies of Developer Relations blog Question of the week Where do I go to learn about GDPR in regards to Google Cloud Platform? Google Cloud: Ready for GDPR blog Google Cloud & the General Data Protection Regulation site Where can you find us next? Mark is speaking at the Monthly SF Game Development Community, presenting on You Can’t Just Add More Servers on May the 30th in San Francisco. Melanie is speaking at a joint WiMLDS and PyLadies event “Paths to Data Science” on June 26th. More details to come.

Hello, welcome to The New Stack Context, a podcast where we review the week's hottest news in cloud-native technologies/at-scale application development and look ahead to topics we expect will gain more attention in coming weeks. This week we start with news from Docker, that its founder and former CTO Solomon Hykes has announced he's leaving the company. Alex Handy first reported that Hykes stepped down as CTO back in November. At the time he said he was staying on as VP of the board of directors. Then this week Hykes published a post on the Docker blog announcing he's leaving the company he started 10 years ago. Alex Handy has the story for us again. Also this week, we discuss Nvidia's AI and deep learning event, the GPU Technology Conference (GTC), with TNS Managing Editor Joab Jackson, who attended the event. The New Stack is ramping up our machine learning coverage, especially as it relates to infrastructure automation and developer tooling. You, our readers and listeners told us in a survey back in December that AI is one of your top 5 areas of interest this year and so we are diving in -- starting with GTC. TNS Editorial Director Libby Clark hosted this episode, with the help of TNS founder Alex Williams.

Talking about Facebook this week is inescapable, so we do, but in a rant-y kind of way. We also discuss Oracle’s plans to hire 10,000 more people in Austin, Solomon Hykes leaving Docker, and the Google/Oracle case around Java’s copyright. Listener Feedback Eric Larson says Coté is wrong there is no zen in pulling weeds. Craig from Ontario says we are doing a great job and emailed for a sticker John Mitchell from Duke Energy got a sticker and did an interview with us here (http://www.softwaredefinedinterviews.com/). That French steak house (https://www.yelp.com/biz/le-relais-de-venise-l-entrec%C3%B4te-paris-2?uid=02uxjke4yV-F3CVOQWN6UA&utm_source=ishare). This episode brought to you by: Datadog! This episode is sponsored by Datadog, a monitoring platform for cloud-scale infrastructure and applications. Built by engineers, for engineers, Datadog provides visibility into more than 200 technologies, including AWS, Chef, and Docker, with built-in metric dashboards and automated alerts. With end-to-end request tracing, Datadog provides visibility into your applications and their underlying infrastructure—all in one place. Sign up for a free trial (https://www.datadoghq.com/ts/tshirt-landingpage/?utm_source=Advertisement&utm_medium=Advertisement&utm_campaign=SoftwareDefinedTalkRead-Tshirt) at www.datadog.com/sdt (http://www.datadog.com/sdt) Datadog wants you to know they provide Container Monitoring (https://www.datadoghq.com/blog/introducing-live-container-monitoring/). You try it out by signing up for a trial at www.datadog.com/sdt (http://www.datadog.com/sdt). Relevant to your interests Oracle's Founder Larry Ellison Says Austin Campus is Going to Grow to 10,000 (http://www.siliconhillsnews.com/2018/03/22/oracles-founder-larry-ellison-says-austin-campus-going-grow-10000-employees/) Google-Oracle high-stakes dustup returns to court — with billions on the line (https://www.mercurynews.com/2018/03/27/google-oracle-high-stakes-dustup-returns-to-court/) Happy as Larry: Why Oracle won the Google Java Android case (https://www.theregister.co.uk/2018/03/29/oracle_google_android/) Pivotal Software files for IPO (https://techcrunch.com/2018/03/23/pivotal-software-files-for-ipo/) Finally, a more coherent IBM story? (https://medium.com/@krishnan/finally-a-more-coherent-ibm-story-f617a7bbc83e?source=rss-62bf9bdc96bc------2) Facebook confirms it records users' call history, stoking furor (https://www.nbcnews.com/tech/social-media/facebook-confirms-it-records-call-history-stoking-privacy-furor-n860006) Getting acquainted with Kubernetes 1.10 (https://coreos.com/blog/kubernetes-110-released), (https://coreos.com/blog/kubernetes-110-released) CoreOS (https://coreos.com/blog/kubernetes-110-released) Red Hat is in the pink: Cracks $3bn revenue run rate as subs take off (https://www.theregister.co.uk/2018/03/27/red_hat_q4_18/) Apollo Is Considering IPO of Cloud-Hosting Firm Rackspace (https://www.bloomberg.com/news/articles/2018-03-27/apollo-is-said-to-consider-ipo-of-cloud-hosting-firm-rackspace?mc_cid=6c6cd5146b&mc_eid=825c180d0b) $13 billion Atlassian explains how the 'joy of missing out' led it to totally reinvent one of its core products (http://www.businessinsider.com/atlassian-stride-hipchat-generally-available-2018-3/) As it shifts cloud focus to platform services, Oracle tries to hold on to its database legacy (https://www.geekwire.com/2018/shifts-cloud-focus-platform-services-oracle-tries-hold-database-legacy/) GitLab 10.6 released with CI/CD for GitHub and deeper Kubernetes integration (https://about.gitlab.com/2018/03/22/gitlab-10-6-released/) Docker, a $1 billion software start-up, has lost its founder a year after new CEO joined (https://news.google.com/news/search/section/q/docker/docker?hl=en&gl=US&ned=us) Solomon Hykes Departs from Docker - The New Stack (https://thenewstack.io/solomon-hykes-departs-from-docker/) Nonsense Honest Status Page (https://mobile.twitter.com/honest_update/status/651897353889259520?lang=en) Boston Dynamics Robot Dog Slips on Banana Peel (https://twitter.com/41Strange/status/972995583370706944) NPR reviews Pacific Rim “Mech & Cheese” (https://www.npr.org/sections/monkeysee/2018/03/22/595179094/pacific-rim-uprising-serves-up-another-helping-of-mech-and-cheese) Conferences, et. al. April 3rd to 4th, Dallas - MC Coté at SpringOne Tour (http://springonetour.io/2018/dallas). April 11th, InnoTech San Antonio (http://www.innotechconferences.com/sanantonio/) - Coté speaking (http://sched.co/Dpzf). April 10-12th, Sydney AWS Summit (https://aws.amazon.com/summits/sydney/) April 26-27, DevOpsDays Jakarta (http://devopsdays.org/events/2018-jakarta/) - Matt (https://twitter.com/agilecircleindo/status/969511498287493120) is keynoting (https://twitter.com/agilecircleindo/status/969511498287493120), and Coté will be speaking too (https://twitter.com/agilecircleindo/status/969511498287493120). May 15th to 18th, 2018 - Coté talking EA at Continuous Lifecycle London (https://continuouslifecycle.london/sessions/the-death-of-enterprise-architecture-defeating-the-devops-microservices-and-cloud-native-assassins/). May 22-25, ChefConf 2018 (https://chefconf.chef.io/), in Chicago. SDT news & hype Check out Software Defined Interviews (http://www.softwaredefinedinterviews.com/), our new podcast. Pretty self-descriptive, plus the #exegesis podcast we’ve been doing, all in one, for free. Keep up with the weekly newsletter (https://us1.campaign-archive.com/home/?u=ce6149b4008d62a08093a4fa6&id=5877922e21). Join us in Slack (http://www.softwaredefinedtalk.com/slack). Buy some t-shirts (https://fsgprints.myshopify.com/collections/software-defined-talk)! DISCOUNT CODE: SDTFSG (20% off) Send your name and address to stickers@softwaredefinedtalk.com (mailto:stickers@softwaredefinedtalk.com) and we will send you a sticker. Recommendations Matt: Disrupting Dystopia - The Bruce Sterling Talk - SXSW 2018 by SXSW (https://soundcloud.com/officialsxsw/disrupting-dystopia-the-bruce-sterling-talk-sxsw-2018) rainbow-delimiters (https://github.com/Fanael/rainbow-delimiters) for Emacs Brandon: Netflix (https://www.netflix.com/title/80046694) The Gift (https://www.netflix.com/title/80046694). Coté: Blue Diamond Smoke House Almonds (https://www.costco.com/Blue-Diamond-Smokehouse-Almonds-45-oz.-.product.100368188.html).

Solomon Hykes joined the show to talk about all things Docker, Moby Project, and what makes Go a good fit for container management.

Solomon Hykes joined the show to talk about all things Docker, Moby Project, and what makes Go a good fit for container management.

Solomon Hykes joined the show to talk about all things Docker, Moby Project, and what makes Go a good fit for container management.

Docker Distributed Systems Summit Opening Words by Solomon Hykes by Docker

Eventually, you have to decide how your open source software is going to make money, and your partners probably won’t like it. That’s what the dust-up around Docker is this week, it seems to us. We also talk briefly about VMware’s big conference this week, and rumors of HPE selling off it’s Software group to private equity. Listen above, subscribe to the feed (http://feeds.feedburner.com/SoftwareDefinedTalk) (or iTunes (https://itunes.apple.com/us/podcast/software-defined-talk-podcast/id893738521?mt=2)), or download the MP3 directly (https://aphid.fireside.fm/d/1437767933/9b74150b-3553-49dc-8332-f89bbbba9f92/ea25eafd-1d31-4f4f-a3a6-efad5b9cd5a5.mp3). With Brandon Whichard (https://twitter.com/bwhichard), Matt Ray (https://twitter.com/mattray), and Coté (https://twitter.com/cote). SPONSOR Check out the multi-cloud webinar lead-gen free (http://www.youtube.com/watch?v=BO2gizEI5O8)! I really like Brian’s part and then the discussion at the end between all of us. I have a discount code for Operability.IO, September 19th and 20th in London. I hear good things about this conference; check out their talks from last year (https://www.youtube.com/playlist?list=PLK4VB0cauli7-_RIvpmn651ePtddw9_Fp). It has a good list of speakers, including our very own Casey West. You can 10% off registration if you use the code COTEMEMOOIO16 (https://ti.to/highops/operability-io-2016/discount/COTEMEMOOIO16). Check out cote.io/promos (https://cote.io/promos/) for more - free books, free cloud time, etc. Show notes Nippers (https://en.wikipedia.org/wiki/Nippers) - "Nippers learn about safety at the beach. They learn about dangers such as rocks, and animals (e.g. the blue-ringed octopus), and also about surf conditions, such as rip currents, sandbars, and waves. Older Nippers also learn some basic first aid and may also learn CPR when they reach the age of 13." Can someone explain this “Docker forking” hoopla? Coté’s write-up (https://cote.io/2016/09/01/deciding-where-the-docker-ecosystem-will-make-money/). Docker Inc. doesn’t want to be a commoditized building block (http://thenewstack.io/docker-fork-talk-split-now-table/) From a Red Hat person (https://www.linkedin.com/pulse/forking-docker-daniel-riek): “The conflict started to escalate earlier this summer, when Docker Inc used its controlling position to push Swarm, it’s own clone of Kubernetes-style container orchestration, into the core Docker project, putting the basic container runtime in a conflict with a notable part of its ecosystem. Docker Inc. then went on to essentially accuse Red Hat of forking Docker - at the Red Hat Summit no less. After that, Docker Inc’s Solomon Hykes came out strongly against the efforts to standardize the container runtime in OCI - an initiative his company co-founded.” Re: that episode where we discuss Docker ecosystem challenges (https://cote.io/2015/04/17/sdt30/): “Yet on a regular basis, Red Hat patches that enable valid requirements from Red Hat customer use cases get shut down as it seems for the simple reason that they don’t fit into Docker Inc’s business strategy.” A fight over where to draw the line between free/open/commodified and costs/proprietary/competitive: "And while I personally consider the orchestration layer the key to the container paradigm, the right approach here is to keep the orchestration separate from the core container runtime standardization. This avoids conflicts between different layers of the container runtime: we can agree on the common container package format, transport, and execution model without limiting choice between e.g. Kubernetes, Mesos, Swarm." Don't bring a pistol to a bazooka fight. Enterprises love RHEL - have you ever tried to sell Ubuntu into organizations? It’s like what selling NT must have been like. VMware hybrid cloud solutionaring Brief notebook from Coté (https://cote.io/2016/08/30/vmwares-foundation-is-a-solution-bundling-of-hybrid-cloud-software/). More coverage (http://www.forbes.com/sites/alexkonrad/2016/08/29/ibm-vmware-deepen-hybrid-cloud-partnership-for-customers-like-marriott/#629acff12853) Keywords “mostly cloud” A representative, not too poorly supported VMware obit (http://www.theregister.co.uk/2016/08/31/thoughts_from_vmworld_2016_is_vmware_becoming_synonymous_with_legacy/) NSX up in the cloud (http://www.techrepublic.com/article/vmworld-2016-vmware-lays-out-its-strategy-for-cross-cloud-support/) This Week in Tech Private Equity… HPE looking to sell off Software group (http://finance.yahoo.com/news/exclusive-hp-enterprise-talks-sell-181749881.html?soc_src=social-sh&soc_trk=tw), sources say. “hoping it can fetch between $8 billion and $10 billion” “HPE's software unit generated $3.6 billion in net revenue (http://quickbooks.intuit.com/r/revenue/understanding-top-bottom-line-difference-net-revenue-net-income/) in 2015, down from $3.9 billion in 2014.” Dell/EMC thing set to close on Sep 7th, 2016 (http://www.businesswire.com/news/home/20160830006294/en/Historic-Dell-EMC-Transaction-Set-Close-September) Quest Software, One Identity To Operate Separately From SonicWall After Dell Software Sale (http://www.crn.com/news/security/300081913/quest-software-one-identity-to-operate-separately-from-sonicwall-after-dell-software-sale.htm) BONUS LINKS! Not covered in podcast. Spaces vs. Tabs The data delivers the truth (spaces) (https://medium.com/@hoffa/400-000-github-repositories-1-billion-files-14-terabytes-of-code-spaces-or-tabs-7cfe0b5dd7fd#.m4axg5pe7) Recommendations Matt: Bubble-sort algorithm explained with Hungarian ("Csángó") folk dance (https://www.youtube.com/watch?v=lyZQPjUT5B4) Brandon: LastChanceU (https://www.netflix.com/title/80091742) Coté: Ulysses (https://itunes.apple.com/us/app/ulysses/id950335311?mt=8&at=1010lohg) - I don’t think there’s any expensive text editors left for me to buy. [This American Life's Worst Song Ever], hear it (https://www.youtube.com/watch?v=-gPuH1yeZ08).

In this episode of Startup School Radio, Y Combinator partner and host Kat Manalac interviews Solomon Hykes, the founder of Docker

Our guest on the podcast this week is Solomon Hykes, Founder and CTO at Docker. We discuss Docker’s upcoming third birthday and how they have been able to grow an entrepreneurial and engineering-focused team that moves quickly. We look at innovations in internet of things and the importance of Docker’s recent acquisition of Unikernel Systems.

DramaFever started running Docker in October of 2013. That makes them one of the first, especially considering Solomon Hykes only shared Docker with the world in April of that year. It also made DramaFever's Bridget Kramhout and Tim Gross pretty decent guests for this 50th episode of The New Stack Analysts that we recorded this week at DockerCon. Watch on YouTube: https://www.youtube.com/watch?v=pN5kaGAIyFA Learn more at: https://thenewstack.io/tns-analysts-show-50-docker-for-today-and-tomorrow-from-dockercon/

Dave and Gunnar talk with one of their favorite partners: Nirmal Mehta of Booz Allen Hamilton, Red Hat Innovation Award winner in 2013. It’s a nerdfest. And a Dockerfest. Highlights Hey Nirmal: His name is Solomon Hykes. Atomic Project the container certification program Vagrant Nirmal wants a workflow. the Devnation Netflix session: it’s what Docker enables. the systemd session Open Source: yes, we actually buy that stuff. Chris works on BPMS, and it’s nice to know that it’s Chris. BAH’s Open Broker Platform = CloudForms + JBoss Fuse Dan Walsh’s Dockah Dockah Dockah

Aaron talks with Solomon Hykes (Founder & CTO) and Ben Golub (CEO) at dotCloud about containers as the next big thing in a post virtual machine world. We dive into dotCloud’s new product, Docker, and talk about feedback to the project and product at OSCON.

Adam Stacoviak and Andrew Thorp wrap-up with Solomon Hykes, the founder & CEO of DotCloud and the creator of Docker.

Mini-cast from AWS re:Invent: Aaron speaks with Solomon Hykes from dotCloud about developing apps for public cloud and differences in PaaS platforms