<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Linux on kenops</title><link>https://www.kenops.io/tags/linux/</link><description>Recent content in Linux on kenops</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sun, 11 Sep 2022 02:45:10 +0000</lastBuildDate><atom:link href="https://www.kenops.io/tags/linux/index.xml" rel="self" type="application/rss+xml"/><item><title>Octoprint container in Debian Windows WSL 2 and Docker Desktop</title><link>https://www.kenops.io/posts/octoprint-container-in-debian-windows-wsl-2/</link><pubDate>Sun, 11 Sep 2022 02:45:10 +0000</pubDate><guid>https://www.kenops.io/posts/octoprint-container-in-debian-windows-wsl-2/</guid><description>&lt;p&gt;Here&amp;rsquo;s a list of steps to get octoprint to run within a container on Windows. I happen to have a windows system running next to my ender so instead of infinitely waiting for a raspberry pi I decided to run octoprint in a container within windows - if possible. Using Debian was a challenge, but I prefer it over Ubuntu, so I took the extra time to figure it out. Enjoy!&lt;/p&gt;</description></item><item><title>Docker volume backup and restore the easy way.</title><link>https://www.kenops.io/posts/docker-volume-backup-and-restore-the-easy-way/</link><pubDate>Mon, 29 Aug 2022 21:06:02 +0000</pubDate><guid>https://www.kenops.io/posts/docker-volume-backup-and-restore-the-easy-way/</guid><description>&lt;p&gt;I haven&amp;rsquo;t had to move docker volumes around in a few years, but I finally had the need today. As usual, I searched for the process, knowing that most examples are&amp;hellip; well&amp;hellip; not very good. Well, as I almost resorted to pulling a manual job using ubuntu, I found a great write-up by Jarek Lipski on Medium. Here&amp;rsquo;s how you backup using alpine and tar. Also, make sure you &amp;ldquo;docker stop&amp;rdquo; the containers that use the volume, so you get a consistent backup.&lt;/p&gt;</description></item><item><title>Password-less ssh in 2 Glorious Steps...</title><link>https://www.kenops.io/posts/password-less-ssh-in-2-glorious-steps/</link><pubDate>Wed, 17 Jun 2020 23:54:55 +0000</pubDate><guid>https://www.kenops.io/posts/password-less-ssh-in-2-glorious-steps/</guid><description>&lt;p&gt;&lt;img loading="lazy" src="https://www.ionos.com/digitalguide/fileadmin/DigitalGuide/Teaser/public-key-authentifizierung-t.jpg"&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Local System - Let&amp;rsquo;s call it alpha&lt;/strong&gt;&lt;br&gt;
&lt;strong&gt;Remote System we don&amp;rsquo;t want to have to enter passwords for,&lt;/strong&gt;&lt;br&gt;
&lt;strong&gt;Let&amp;rsquo;s call it foxtrot&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Prep:&lt;/strong&gt; Harden your existing ssh keys since RSA 1024 sucks. This will create a new 4096 version - ed22519 is actually preferred so you can skip the rsa creation if preferred.&lt;/p&gt;
&lt;pre tabindex="0"&gt;&lt;code&gt;me@alpha$ mv ~/.ssh/id_rsa ~/.ssh/id_rsa_legacy
me@alpha$ mv ~/.ssh/id_rsa.pub ~/.ssh/id_rsa_legacy.pub
&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;&lt;strong&gt;Step 1:&lt;/strong&gt; Generate new keys:&lt;/p&gt;
&lt;pre tabindex="0"&gt;&lt;code&gt;me@alpha$ ssh-keygen -t rsa -b 4096 -o -a 100 #RSA version
me@alpha$ ssh-keygen -o -a 100 -t ed25519 #Preferred ed25519 version
&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;&lt;strong&gt;Step 2:&lt;/strong&gt; Copy the Ed25519  keys to the remote system called foxtrot:&lt;/p&gt;</description></item></channel></rss>