<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Ops on Alessandro Miliucci</title><link>https://miliucci.org/tags/ops/</link><description>Recent content in Ops on Alessandro Miliucci</description><generator>Hugo</generator><language>en-gb</language><copyright>© Alessandro Miliucci</copyright><lastBuildDate>Tue, 12 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://miliucci.org/tags/ops/index.xml" rel="self" type="application/rss+xml"/><item><title>How to edit environment variables in a running Docker container</title><link>https://miliucci.org/note/edit-env-vars-running-docker-container/</link><pubDate>Tue, 12 May 2026 00:00:00 +0000</pubDate><guid>https://miliucci.org/note/edit-env-vars-running-docker-container/</guid><description>&lt;p>Docker does not support a direct method for updating environment variables for a running container.
This is something you can not call &amp;ldquo;a bug&amp;rdquo; because it is consistent with the &lt;em>immutable&lt;/em> way Docker runs application.
For this reason, the common way to update an environment variable is to re-create the container from the image.
Sometimes this can not be done because your container has a &lt;em>state&lt;/em> that must be preserved, especially if you are hacking on your machine.
If you need to update them, three steps are required.
Since I have to do this from time to time, I decided to write this note.&lt;/p></description></item></channel></rss>