<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>grimmory &amp;mdash; Marcin Modest Trzaska</title>
    <link>https://blog.argilus.online/czach/tag:grimmory</link>
    <description>Piszę, co mi przyjdzie do głowy. Na tematy różne.</description>
    <pubDate>Tue, 06 Oct 2026 21:56:18 +0200</pubDate>
    <item>
      <title>Grimory </title>
      <link>https://blog.argilus.online/czach/grimory</link>
      <description>&lt;![CDATA[Na dzień dobry - brak kawy. Skończyła się. Znaczy ta bezkofeinowa. Placebo z rana. Potem aktualizacja Grimory w Dockerze. &#xA;&#xA;Nic tam nie ruszałem a pełno błędów.&#xA;&#xA;$ sudo docker compose pull &amp;&amp; sudo docker compose up -d &amp;&amp; sudo docker image prune -f &#xA;yaml: while parsing a block mapping at line 1, column 3: line 22, column 4: did not find expected key&#xA;&#xA;I tak w dwóch miejscach. Wcięcia się nie podobały w docker-compose.yml.&#xA;&#xA;A później — jeszcze lepiej:&#xA;&#xA;$ sudo docker compose pull &amp;&amp; sudo docker compose up -d &amp;&amp; sudo docker image prune -f &#xA;[+] pull 2/2&#xA; ✔ Image grimmory/grimmory:latest           Pulled                                                                                                                             0.9s&#xA; ✔ Image lscr.io/linuxserver/mariadb:11.4.5 Pulled                                                                                                                             1.1s&#xA;[+] up 1/1&#xA; ✘ Contain... Error response from daemon: Conflict. The container name &#34;/mariadb&#34; is already in use by container &#34;52aa973123812b440acab7f257f1c82c11d0955b4f7297cf3df939dbe1dcb12c&#34;. You have to remove (or rename) that container to be able to reuse that name. 0.0s&#xA;Error response from daemon: Conflict. The container name &#34;/mariadb&#34; is already in use by container &#34;52aa973123812b440acab7f257f1c82c11d0955b4f7297cf3df939dbe1dcb12c&#34;. You have to remove (or rename) that container to be able to reuse that name.&#xA;$ sudo docker rm -f mariadb &amp;&amp; sudo docker compose up -d&#xA;mariadb&#xA;[+] up 1/2&#xA; ✔ Container mariadb Healthy                                                                                                                                                   5.7s&#xA; ⠸ Container grimory Starting                                                                                                                                                  5.9s&#xA;Error response from daemon: failed to set up container networking: driver failed programming external connectivity on endpoint grimory (cbaf0f9b92de56ca146fa409f048a2006818886df531fd5fe37a343f9e2e0244): Bind for 0.0.0.0:6060 failed: port is already allocated&#xA;$ sudo docker ps | grep 6060&#xA;26dd551ae886   d35cf2753c67                                                     &#34;/usr/local/bin/entr…&#34;   3 weeks ago      Up 3 weeks (healthy)        0.0.0.0:6060-  6060/tcp, [::]:6060-  6060/tcp                                                          booklore&#xA;$ sudo docker rm -f booklore&#xA;WTF? Skąd tam się wzięło booklore — przecież kilka miesięcy temu zastąpiłem to właśnie Grimory?!&#xA;&#xA;Ale poszło w końcu:&#xA;$ sudo docker compose pull &amp;&amp; sudo docker compose up -d &amp;&amp; sudo docker image prune -f &#xA;[+] pull 2/2&#xA; ✔ Image lscr.io/linuxserver/mariadb:11.4.5 Pulled                                                                                                                             1.2s&#xA; ✔ Image grimmory/grimmory:latest           Pulled                                                                                                                             1.1s&#xA;[+] up 2/2&#xA; ✔ Container mariadb Healthy                                                                                                                                                   0.5s&#xA; ✔ Container grimory Started                                                                                                                                                   0.1s&#xA;Deleted Images:&#xA;untagged: grimmory/grimmory@sha256:fffd0ae0bfccd64ca00441e8fa58a14e286b9115e5df1cb47eecf294ad09e6ff&#xA;deleted: sha256:d35cf2753c677d31165845383f86417225d8a1f3b9126d9ba7312d834d996feb&#xA;deleted: sha256:90e89d354d35b795e700b78a50aef55188cdc59d3a3acf7c3bf3feece59c2683&#xA;&#xA;Total reclaimed space: 107.4MB&#xA;&#xA;#docker #grimmory #booklore&#xA;&#xA;-- &#xD;&#xA;Marcin &#34;czach&#34; Trzaska&#xD;&#xA;reply-to: @czach@mastodon.argilus.online]]&gt;</description>
      <content:encoded><![CDATA[<p>Na dzień dobry – brak kawy. Skończyła się. Znaczy ta bezkofeinowa. Placebo z rana. Potem aktualizacja <a href="https://github.com/grimmory-tools/grimmory" rel="nofollow"><em>Grimory</em></a> w <em>Dockerze</em>.</p>

<p>Nic tam nie ruszałem a pełno błędów.</p>

<pre><code>$ sudo docker compose pull &amp;&amp; sudo docker compose up -d &amp;&amp; sudo docker image prune -f 
yaml: while parsing a block mapping at line 1, column 3: line 22, column 4: did not find expected key
</code></pre>

<p>I tak w dwóch miejscach. Wcięcia się nie podobały w <em>docker-compose.yml</em>.</p>

<p>A później — jeszcze lepiej:</p>

<pre><code>$ sudo docker compose pull &amp;&amp; sudo docker compose up -d &amp;&amp; sudo docker image prune -f 
[+] pull 2/2
 ✔ Image grimmory/grimmory:latest           Pulled                                                                                                                             0.9s
 ✔ Image lscr.io/linuxserver/mariadb:11.4.5 Pulled                                                                                                                             1.1s
[+] up 1/1
 ✘ Contain... Error response from daemon: Conflict. The container name &#34;/mariadb&#34; is already in use by container &#34;52aa973123812b440acab7f257f1c82c11d0955b4f7297cf3df939dbe1dcb12c&#34;. You have to remove (or rename) that container to be able to reuse that name. 0.0s
Error response from daemon: Conflict. The container name &#34;/mariadb&#34; is already in use by container &#34;52aa973123812b440acab7f257f1c82c11d0955b4f7297cf3df939dbe1dcb12c&#34;. You have to remove (or rename) that container to be able to reuse that name.
$ sudo docker rm -f mariadb &amp;&amp; sudo docker compose up -d
mariadb
[+] up 1/2
 ✔ Container mariadb Healthy                                                                                                                                                   5.7s
 ⠸ Container grimory Starting                                                                                                                                                  5.9s
Error response from daemon: failed to set up container networking: driver failed programming external connectivity on endpoint grimory (cbaf0f9b92de56ca146fa409f048a2006818886df531fd5fe37a343f9e2e0244): Bind for 0.0.0.0:6060 failed: port is already allocated
$ sudo docker ps | grep 6060
26dd551ae886   d35cf2753c67                                                     &#34;/usr/local/bin/entr…&#34;   3 weeks ago      Up 3 weeks (healthy)        0.0.0.0:6060-&gt;6060/tcp, [::]:6060-&gt;6060/tcp                                                          booklore
$ sudo docker rm -f booklore
</code></pre>

<p>WTF? Skąd tam się wzięło <em>booklore</em> — przecież kilka miesięcy temu zastąpiłem to właśnie <em>Grimory</em>?!</p>

<p>Ale poszło w końcu:</p>

<pre><code>$ sudo docker compose pull &amp;&amp; sudo docker compose up -d &amp;&amp; sudo docker image prune -f 
[+] pull 2/2
 ✔ Image lscr.io/linuxserver/mariadb:11.4.5 Pulled                                                                                                                             1.2s
 ✔ Image grimmory/grimmory:latest           Pulled                                                                                                                             1.1s
[+] up 2/2
 ✔ Container mariadb Healthy                                                                                                                                                   0.5s
 ✔ Container grimory Started                                                                                                                                                   0.1s
Deleted Images:
untagged: grimmory/grimmory@sha256:fffd0ae0bfccd64ca00441e8fa58a14e286b9115e5df1cb47eecf294ad09e6ff
deleted: sha256:d35cf2753c677d31165845383f86417225d8a1f3b9126d9ba7312d834d996feb
deleted: sha256:90e89d354d35b795e700b78a50aef55188cdc59d3a3acf7c3bf3feece59c2683

Total reclaimed space: 107.4MB
</code></pre>

<p><a href="/czach/tag:docker" class="hashtag" rel="nofollow"><span>#</span><span class="p-category">docker</span></a> <a href="/czach/tag:grimmory" class="hashtag" rel="nofollow"><span>#</span><span class="p-category">grimmory</span></a> <a href="/czach/tag:booklore" class="hashtag" rel="nofollow"><span>#</span><span class="p-category">booklore</span></a></p>

<p>—
Marcin “czach” Trzaska
reply-to: <a href="https://blog.argilus.online/@/czach@mastodon.argilus.online" class="u-url mention" rel="nofollow">@<span>czach@mastodon.argilus.online</span></a></p>
]]></content:encoded>
      <guid>https://blog.argilus.online/czach/grimory</guid>
      <pubDate>Tue, 15 Sep 2026 06:42:11 +0000</pubDate>
    </item>
  </channel>
</rss>