<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Virtual-Machine on ads' corner</title><link>https://andreas.scherbaum.la/tags/virtual-machine/</link><description>Recent content in Virtual-Machine on ads' corner</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 07 May 2025 00:00:00 +0200</lastBuildDate><atom:link href="https://andreas.scherbaum.la/tags/virtual-machine/index.xml" rel="self" type="application/rss+xml"/><item><title>Show all docker build output</title><link>https://andreas.scherbaum.la/post/2025-05-07_show-all-docker-build-output/</link><pubDate>Wed, 07 May 2025 00:00:00 +0200</pubDate><guid>https://andreas.scherbaum.la/post/2025-05-07_show-all-docker-build-output/</guid><description>&lt;p&gt;&lt;em&gt;Docker&lt;/em&gt; by default will hide the process output of a step once the step is completed. This makes for a nice and tidy output, not overloading the screen with too many details. Here&amp;rsquo;s such an example:&lt;/p&gt;&#10;&lt;div class="highlight"&gt;&lt;div style="background-color:#f7f7f7;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;"&gt;&#10;&lt;table style="border-spacing:0;padding:0;margin:0;border:0;"&gt;&lt;tr&gt;&lt;td style="vertical-align:top;padding:0;margin:0;border:0;"&gt;&#10;&lt;pre tabindex="0" style="background-color:#f7f7f7;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;"&gt;&lt;code&gt;&lt;span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f"&gt;1&#10;&lt;/span&gt;&lt;span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f"&gt;2&#10;&lt;/span&gt;&lt;span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f"&gt;3&#10;&lt;/span&gt;&lt;span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f"&gt;4&#10;&lt;/span&gt;&lt;span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f"&gt;5&#10;&lt;/span&gt;&lt;span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f"&gt;6&#10;&lt;/span&gt;&lt;span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f"&gt;7&#10;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/td&gt;&#10;&lt;td style="vertical-align:top;padding:0;margin:0;border:0;;width:100%"&gt;&#10;&lt;pre tabindex="0" style="background-color:#f7f7f7;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;"&gt;&lt;code class="language-docker" data-lang="docker"&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;&lt;span style="color:#953800"&gt;DOCKER_BUILDKIT&lt;/span&gt;&lt;span style="color:#0550ae"&gt;=&lt;/span&gt;&lt;span style="color:#0550ae"&gt;1&lt;/span&gt; docker compose up --force-recreate --build&lt;span style="color:#f6f8fa;background-color:#82071e"&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;&lt;span style="color:#f6f8fa;background-color:#82071e"&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt; &lt;span style="color:#0550ae"&gt;=&lt;/span&gt;&amp;gt; &lt;span style="color:#0550ae"&gt;[&lt;/span&gt;&lt;span style="color:#6639ba"&gt;test&lt;/span&gt; build-stage 2/20&lt;span style="color:#0550ae"&gt;]&lt;/span&gt; RUN &lt;span style="color:#6639ba"&gt;echo&lt;/span&gt; &lt;span style="color:#0a3069"&gt;&amp;#34;Checksum /etc/hosts&amp;#34;&lt;/span&gt; 0.5s&lt;span style="color:#f6f8fa;background-color:#82071e"&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt; &lt;span style="color:#0550ae"&gt;=&lt;/span&gt;&amp;gt; &lt;span style="color:#0550ae"&gt;[&lt;/span&gt;&lt;span style="color:#6639ba"&gt;test&lt;/span&gt; build-stage 3/20&lt;span style="color:#0550ae"&gt;]&lt;/span&gt; RUN sha256sum /etc/hosts 0.3s&lt;span style="color:#f6f8fa;background-color:#82071e"&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;&lt;span style="color:#f6f8fa;background-color:#82071e"&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt; &lt;span style="color:#0550ae"&gt;=&lt;/span&gt;&amp;gt; &lt;span style="color:#0550ae"&gt;[&lt;/span&gt;&lt;span style="color:#6639ba"&gt;test&lt;/span&gt; build-stage 2/20&lt;span style="color:#0550ae"&gt;]&lt;/span&gt; RUN &lt;span style="color:#6639ba"&gt;echo&lt;/span&gt; &lt;span style="color:#0a3069"&gt;&amp;#34;Checksum /etc/hosts&amp;#34;&lt;/span&gt; 0.6s&lt;span style="color:#f6f8fa;background-color:#82071e"&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt; &lt;span style="color:#0550ae"&gt;=&lt;/span&gt;&amp;gt; &lt;span style="color:#0550ae"&gt;[&lt;/span&gt;&lt;span style="color:#6639ba"&gt;test&lt;/span&gt; build-stage 3/20&lt;span style="color:#0550ae"&gt;]&lt;/span&gt; RUN sha256sum /etc/hosts 0.3s&lt;span style="color:#f6f8fa;background-color:#82071e"&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/table&gt;&#10;&lt;/div&gt;&#10;&lt;/div&gt;&lt;p&gt;As you can see, the actual &lt;code&gt;sha256sum&lt;/code&gt; checksum is not shown once the steps complete.&lt;/p&gt;</description></item><item><title>Autostart XEN Domains</title><link>https://andreas.scherbaum.la/post/2013-06-15_autostart-xen-domains/</link><pubDate>Sat, 15 Jun 2013 21:52:00 +0200</pubDate><guid>https://andreas.scherbaum.la/post/2013-06-15_autostart-xen-domains/</guid><description>&lt;p&gt;When using &lt;em&gt;XEN&lt;/em&gt; you can start virtual machines using &lt;code&gt;xm create&lt;/code&gt;. However after rebooting the host machine, the virtual machines are not started automatically. This minor problem is easy to solve. Let&amp;rsquo;s say the configuration for the virtual machine is in &lt;code&gt;/etc/xen/pluto.cfg&lt;/code&gt;:&lt;/p&gt;</description></item><item><title>Greenplum Community Edition - Connections from the host system into the virtual machine</title><link>https://andreas.scherbaum.la/post/2012-08-18_greenplum-community-edition-connections-from-the-host-system-into-the-virtual-machine/</link><pubDate>Sat, 18 Aug 2012 21:22:40 +0200</pubDate><guid>https://andreas.scherbaum.la/post/2012-08-18_greenplum-community-edition-connections-from-the-host-system-into-the-virtual-machine/</guid><description>&lt;p&gt;If you download the &lt;a href="https://web.archive.org/web/20120416175103/http://www.greenplum.com/community/downloads/database-ce/"&gt;Greenplum Community Edition&lt;/a&gt; (GP CE) from the &lt;em&gt;Greenplum&lt;/em&gt; website and if you want to connect tools like &lt;a href="https://www.pgadmin.org/"&gt;pgAdminIII&lt;/a&gt; from your host machine to the database inside the virtual machine, you have to disable the firewall. The CE is installed on &lt;a href="https://www.centos.org/"&gt;CentOS&lt;/a&gt; and by default the &lt;a href="https://en.wikipedia.org/wiki/Firewall_(computing)"&gt;firewall&lt;/a&gt; is enabled and blocks connections from outside to most ports.&lt;/p&gt;&#10;&lt;p&gt;Here are the steps which are required to disable the firewall:&lt;/p&gt;</description></item></channel></rss>