Deployed 37adecb with MkDocs version: 1.5.3

install/index.html

@@ -42,7 +42,7 @@
 </span><span id=__span-12-7><a id=__codelineno-12-7 name=__codelineno-12-7 href=#__codelineno-12-7></a>
 </span><span id=__span-12-8><a id=__codelineno-12-8 name=__codelineno-12-8 href=#__codelineno-12-8></a><span class=c1># install specific release with yum</span>
 </span><span id=__span-12-9><a id=__codelineno-12-9 name=__codelineno-12-9 href=#__codelineno-12-9></a>yum<span class=w> </span>install<span class=w> </span>https://github.com/srl-labs/containerlab/releases/download/v0.7.0/containerlab_0.7.0_linux_386.rpm
-</span></code></pre></div> </details> <p>The package installer will put the <code>containerlab</code> binary in the <code>/usr/bin</code> directory as well as create the <code>/usr/bin/clab -&gt; /usr/bin/containerlab</code> symlink. The symlink allows the users to save on typing when they use containerlab: <code>clab &lt;command&gt;</code>.</p> <h2 id=windows>Windows<a class=headerlink href=#windows title="Permanent link">#</a></h2> <p>Containerlab runs on Windows powered by Windows Subsystem Linux (aka WSL), where you can run Containerlab directly or in a Devcontainer. Open up <a href=../windows/ >Containerlab on Windows</a> documentation for more details.</p> <h2 id=apple-macos>Apple macOS<a class=headerlink href=#apple-macos title="Permanent link">#</a></h2> <p>Running containerlab on macOS is possible both on ARM (M1/M2/M3/etc) and Intel chipsets. For a long time, we had many caveats around M-chipsets on Macs, but with the introduction of ARM64-native NOSes like Nokia SR Linux and Arista cEOS, powered by Rosetta emulation for x86_64-based NOSes, it is now possible to run containerlab on ARM-based Macs.</p> <p>Since we wanted to share our experience with running containerlab on macOS in details, we have created a separate - <a href=../macos/ >Containerlab on macOS</a> - guide.</p> <h2 id=container>Container<a class=headerlink href=#container title="Permanent link">#</a></h2> <p>Containerlab is also available in a container packaging. The latest containerlab release can be pulled with:</p> <div class="language-text highlight"><pre><span></span><code><span id=__span-13-1><a id=__codelineno-13-1 name=__codelineno-13-1 href=#__codelineno-13-1></a>docker pull ghcr.io/srl-labs/clab
+</span></code></pre></div> </details> <p>The package installer will put the <code>containerlab</code> binary in the <code>/usr/bin</code> directory as well as create the <code>/usr/bin/clab -&gt; /usr/bin/containerlab</code> symlink. The symlink allows the users to save on typing when they use containerlab: <code>clab &lt;command&gt;</code>.</p> <h2 id=windows>Windows<a class=headerlink href=#windows title="Permanent link">#</a></h2> <p>Containerlab runs on Windows powered by Windows Subsystem Linux (aka WSL), where you can run Containerlab directly or in a Devcontainer. Open up <a href=../windows/ ><strong>Containerlab on Windows</strong></a> documentation for more details.</p> <h2 id=apple-macos>Apple macOS<a class=headerlink href=#apple-macos title="Permanent link">#</a></h2> <p>Running containerlab on macOS is possible both on ARM (M1/M2/M3/etc) and Intel chipsets. For a long time, we had many caveats around M-chipsets on Macs, but with the introduction of ARM64-native NOSes like Nokia SR Linux and Arista cEOS, powered by Rosetta emulation for x86_64-based NOSes, it is now possible to run containerlab on ARM-based Macs.</p> <p>Since we wanted to share our experience with running containerlab on macOS in details, we have created a separate - <a href=../macos/ ><strong>Containerlab on macOS</strong></a> - guide.</p> <h2 id=container>Container<a class=headerlink href=#container title="Permanent link">#</a></h2> <p>Containerlab is also available in a container packaging. The latest containerlab release can be pulled with:</p> <div class="language-text highlight"><pre><span></span><code><span id=__span-13-1><a id=__codelineno-13-1 name=__codelineno-13-1 href=#__codelineno-13-1></a>docker pull ghcr.io/srl-labs/clab
 </span></code></pre></div> <p>To pick any of the released versions starting from release 0.19.0, use the version number as a tag, for example, <code>docker pull ghcr.io/srl-labs/clab:0.19.0</code></p> <p>Since containerlab itself deploys containers and creates veth pairs, its run instructions are a bit more complex, but still, it is a copy-paste-able command.</p> <p>For example, if your lab files are contained within the current working directory - <code>$(pwd)</code> - then you can launch containerlab container as follows:</p> <div class="language-bash highlight"><pre><span></span><code><span id=__span-14-1><a id=__codelineno-14-1 name=__codelineno-14-1 href=#__codelineno-14-1></a>docker<span class=w> </span>run<span class=w> </span>--rm<span class=w> </span>-it<span class=w> </span>--privileged<span class=w> </span><span class=se>\</span>
 </span><span id=__span-14-2><a id=__codelineno-14-2 name=__codelineno-14-2 href=#__codelineno-14-2></a><span class=w>    </span>--network<span class=w> </span>host<span class=w> </span><span class=se>\</span>
 </span><span id=__span-14-3><a id=__codelineno-14-3 name=__codelineno-14-3 href=#__codelineno-14-3></a><span class=w>    </span>-v<span class=w> </span>/var/run/docker.sock:/var/run/docker.sock<span class=w> </span><span class=se>\</span>