Skip to content

Comments

Adding podman support as a fallback#1315

Open
GreenBlast wants to merge 1 commit intoelie222:mainfrom
GreenBlast:adding-podman-support-to-install-process
Open

Adding podman support as a fallback#1315
GreenBlast wants to merge 1 commit intoelie222:mainfrom
GreenBlast:adding-podman-support-to-install-process

Conversation

@GreenBlast
Copy link

My mac didn't have docker install but podman, it is almost a drop in replacement, but aliasing docker to podman didn't work. So I vibed this change (Full Disclosure - used opencode).

Seem to be working.

@vercel
Copy link

vercel bot commented Jan 18, 2026

@GreenBlast is attempting to deploy a commit to the Inbox Zero OSS Program Team on Vercel.

A member of the Team first needs to authorize it.

@CLAassistant
Copy link

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

Copy link
Contributor

@cubic-dev-ai cubic-dev-ai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

2 issues found across 1 file

Prompt for AI agents (all issues)

Check if these issues are valid — if so, understand the root cause of each and fix them.


<file name="packages/cli/src/main.ts">

<violation number="1" location="packages/cli/src/main.ts:820">
P1: Podman fallback is unused for start/stop/update: runtime defaults to "docker" and these commands never run detection, so Podman-only environments will still try to execute docker and fail.</violation>

<violation number="2" location="packages/cli/src/main.ts:935">
P2: Compose tool detection ignored: commands still call `${CONTAINER_RUNTIME} compose`, failing when only standalone docker-compose/podman-compose is available</violation>
</file>

Since this is your first cubic review, here's how it works:

  • cubic automatically reviews your code and comments on bugs and improvements
  • Teach cubic by replying to its comments. cubic learns from your replies and gets better over time
  • Ask questions if you need clarification on any suggestion

Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.

}

const upResult = spawnSync("docker", args, {
const upResult = spawnSync(CONTAINER_RUNTIME, args, {
Copy link
Contributor

@cubic-dev-ai cubic-dev-ai bot Jan 18, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1: Podman fallback is unused for start/stop/update: runtime defaults to "docker" and these commands never run detection, so Podman-only environments will still try to execute docker and fail.

Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At packages/cli/src/main.ts, line 820:

<comment>Podman fallback is unused for start/stop/update: runtime defaults to "docker" and these commands never run detection, so Podman-only environments will still try to execute docker and fail.</comment>

<file context>
@@ -782,7 +817,7 @@ async function runStart(options: { detach: boolean }) {
   }
 
-  const upResult = spawnSync("docker", args, {
+  const upResult = spawnSync(CONTAINER_RUNTIME, args, {
     stdio: options.detach ? "pipe" : "inherit",
   });
</file context>
Fix with Cubic

stdio: "inherit",
});
spawnSync(
CONTAINER_RUNTIME,
Copy link
Contributor

@cubic-dev-ai cubic-dev-ai bot Jan 18, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2: Compose tool detection ignored: commands still call ${CONTAINER_RUNTIME} compose, failing when only standalone docker-compose/podman-compose is available

Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At packages/cli/src/main.ts, line 935:

<comment>Compose tool detection ignored: commands still call `${CONTAINER_RUNTIME} compose`, failing when only standalone docker-compose/podman-compose is available</comment>

<file context>
@@ -896,9 +931,13 @@ async function runStatus() {
-    stdio: "inherit",
-  });
+  spawnSync(
+    CONTAINER_RUNTIME,
+    ["compose", "-f", STANDALONE_COMPOSE_FILE, "ps"],
+    {
</file context>
Fix with Cubic

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants