<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Configuration on DRM HSE</title><link>https://www.drmhse.com/tags/configuration/</link><description>Recent content in Configuration on DRM HSE</description><generator>Hugo</generator><language>en</language><lastBuildDate>Wed, 15 Jul 2026 22:43:45 +0300</lastBuildDate><atom:link href="https://www.drmhse.com/tags/configuration/index.xml" rel="self" type="application/rss+xml"/><item><title>Why Docker Compose Restart Ignores Configuration Changes</title><link>https://www.drmhse.com/posts/docker-stop-start-wont-pick-up-changes/</link><pubDate>Wed, 05 Nov 2025 05:20:09 +0000</pubDate><guid>https://www.drmhse.com/posts/docker-stop-start-wont-pick-up-changes/</guid><description>&lt;p>&lt;code>docker compose restart&lt;/code> is not a command for applying a changed Compose file. That distinction would have saved me an annoying debugging session.&lt;/p>
&lt;p>I had changed a bind mount, restarted the service, and still saw the old files. Even stopping and starting the service did not help. The Compose file described the state I wanted, but the existing container still held the configuration with which it had been created.&lt;/p>
&lt;h2 id="restart-brings-back-the-same-container">Restart brings back the same container&lt;/h2>
&lt;p>Consider this small service in &lt;code>compose.yaml&lt;/code> (the same issue applies if the file is named &lt;code>docker-compose.yml&lt;/code>):&lt;/p></description></item></channel></rss>