deploy: 28f45890313af72c1437b88778f1c52a0c026519

This commit is contained in:
davegallant
2021-10-12 01:31:44 +00:00
parent f0ad849e64
commit 3ac4619652
2 changed files with 2 additions and 2 deletions

View File

@@ -179,7 +179,7 @@ Storing signatures
14119a10abf4669e8cdbdff324a9f9605d99697215a0d21c360fe8dfa8471bab
</code></pre><p>*<em>Note: If you&rsquo;re having an issue with pulling images, you may need to remove <code>~/.docker</code>. Rather than removing it entirely, you can simply rename it: <code>mv ~/.docker ~/.docker-backup</code>. (<code>~/.docker/config.json</code> can cause issues with podman.)</em></p>
<p>and then exec into the container:</p>
<pre tabindex=0><code class=language-console data-lang=console>$ podman run -p 8080 --rm -ti alpine
<pre tabindex=0><code class=language-console data-lang=console>$ podman run --rm -ti alpine
Error: error preparing container 99ace1ef8a78118e178372d91fd182e8166c399fbebe0f676af59fbf32ce205b for attach: error configuring network namespace for container 99ace1ef8a78118e178372d91fd182e8166c399fbebe0f676af59fbf32ce205b: error adding pod unruffled_bohr_unruffled_bohr to CNI network &quot;podman&quot;: unexpected end of JSON input
</code></pre><p>What does this error mean? A bit of googling lead to <a href=https://github.com/containers/podman/issues/11837>this github issue</a>.</p>
<p>Until the fix is released, a workaround is to just specify a port (even when it&rsquo;s not needed):</p>