<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Docker on Alexander Junge&#39;s website</title>
    <link>https://www.alexanderjunge.net/categories/docker/</link>
    <description>Recent content in Docker on Alexander Junge&#39;s website</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-US</language>
    <lastBuildDate>Sun, 20 Jan 2019 00:00:00 +0000</lastBuildDate>
    
	<atom:link href="https://www.alexanderjunge.net/categories/docker/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>Trying out Docker Compose</title>
      <link>https://www.alexanderjunge.net/blog/demo-docker-compose/</link>
      <pubDate>Sun, 20 Jan 2019 00:00:00 +0000</pubDate>
      
      <guid>https://www.alexanderjunge.net/blog/demo-docker-compose/</guid>
      <description>Docker containers are well-suited to ship software because they allow a fast, flexible, and efficient deployment in any computing environment - be it on premise, in the cloud, etc. Docker Compose allows users to orchestrate multiple Docker containers that can talk to one another. Docker Compose applications are perfectly suited for providing data science and machine learning infrastructure where multiple tools need to interact to form a development environment.
I played around with Docker Compose over the last couple of days to produce an example of such an environment.</description>
    </item>
    
  </channel>
</rss>