fix: respect LIMA_HOME environment variable

Signed-off-by: Anders F Björklund <anders.f.bjorklund@gmail.com>
containers · Jul 18, 2023 · 49d1b88 · 49d1b88
1 parent 85414b5
commit 49d1b88
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/extensions/lima/src/extension.ts b/extensions/lima/src/extension.ts
@@ -48,8 +48,8 @@ function registerProvider(
 export async function activate(extensionContext: extensionApi.ExtensionContext): Promise<void> {
   const engineType = configuration.getConfiguration('lima').get('type') || 'podman';
   const instanceName = configuration.getConfiguration('lima').get('name') || engineType;
-  const limaHome = os.homedir(); // TODO: look for the LIMA_HOME environment variable
-  const socketPath = path.resolve(limaHome, '.lima/' + instanceName + '/sock/' + engineType + '.sock');
+  const limaHome = 'LIMA_HOME' in process.env ? process.env['LIMA_HOME'] : os.homedir() + '/.lima';
+  const socketPath = path.resolve(limaHome, instanceName + '/sock/' + engineType + '.sock');
 
   let provider;
   if (fs.existsSync(socketPath)) {