<?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>vctl on Why did IT fail</title><link>https://www.why-did-it.fail/tags/vctl/</link><description>Recent content in vctl on Why did IT fail</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>Copyright © 2026 Dominik Textoris (formerly Zorgnotti). All Rights Reserved.</copyright><lastBuildDate>Sat, 20 Nov 2021 00:00:00 +0000</lastBuildDate><atom:link href="https://www.why-did-it.fail/tags/vctl/index.xml" rel="self" type="application/rss+xml"/><item><title>VMware Workstation - vctl unable to start</title><link>https://www.why-did-it.fail/blog/2021-06-conflicting-vmrun-versions/</link><pubDate>Sat, 20 Nov 2021 00:00:00 +0000</pubDate><guid>https://www.why-did-it.fail/blog/2021-06-conflicting-vmrun-versions/</guid><description>Many thanks to Darius Davis from our engineering team who set me up on the solution.
This morning I &amp;ldquo;just wanted to spin up a container quickly&amp;rdquo;. Having a recent version of VMware workstation already on my computer, using vctl was my preferred choice (In case you missed the blog).
Problem My initial plans came to a halt as very attempt of a vctl system config or vctl system start threw an error:</description></item></channel></rss>