<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Docker Compose on</title><link>/tags/docker-compose/</link><description>Recent content in Docker Compose on</description><generator>Hugo</generator><language>en</language><lastBuildDate>Wed, 10 Jul 2024 00:00:00 +0000</lastBuildDate><atom:link href="/tags/docker-compose/index.xml" rel="self" type="application/rss+xml"/><item><title>Running Dex With Docker Compose</title><link>/2024/07/running-dex-with-docker-compose/</link><pubDate>Wed, 10 Jul 2024 00:00:00 +0000</pubDate><guid>/2024/07/running-dex-with-docker-compose/</guid><description>&lt;p>I previously wrote on how to run Dex using docker. In this article, I will create nearly the same setup using docker-compose. This will allow you to run, stop, and restart the setup from a central location.&lt;/p>
&lt;!-- more -->
&lt;h2 id="setting-up-the-docker-compose-file">Setting up the docker-compose file&lt;/h2>
&lt;p>You&amp;rsquo;ll want to make sure that you have the same Dex config file from the previous article but with one small change. The &lt;code>issuer&lt;/code> field should be changed to &lt;code>http://dex:5556/dex&lt;/code> to match the service name that will be used in the docker-compose file. If the &lt;code>issuer&lt;/code> field is not changed, the example app will try to find Dex within the container it is running in and will not be able to reach it. Changing it to &lt;code>http://dex:5556/dex&lt;/code> will allow the example app to reach Dex through the network that docker-compose creates.&lt;/p></description></item></channel></rss>