init generates devcontainer.json referencing non-existent feature ghcr.io/devcontainers/features/podman-in-podman

[kaspergff]

init generates devcontainer.json referencing non-existent feature ghcr.io/devcontainers/features/podman-in-podman

Description

mxcli init generates a .devcontainer/devcontainer.json that references the dev container feature ghcr.io/devcontainers/features/podman-in-podman:1. This feature does not exist in the official devcontainers/features registry, so the dev container build fails when resolving features.

This reproduces on v0.11.0, which is currently the latest release, so it is not fixed by upgrading.

Environment

mxcli version	v0.11.0 (2026-05-21T18:04:46Z) (latest release)
Mendix version	11.8.0
OS	Windows 10 (build 26100)
Container runtime	Podman 5.8.2 (rootless), via Podman Desktop on WSL2
VS Code Dev Containers extension	0.459.1
Dev Containers CLI	0.86.1

Additionally, the source path https://github.com/devcontainers/features/tree/main/src/podman-in-podman returns 404. The official devcontainers/features repository does not publish a podman-in-podman feature, so this reference can never resolve.

Question

What is the intended feature here?

• Should this be ghcr.io/devcontainers/features/docker-in-docker?
• A specific community-published podman-in-podman feature (which full path / namespace)?
• Or a custom setup via the Dockerfile / postCreateCommand instead of a feature?

Happy to test a fix. I can also provide a mxcli diag --bundle privately if needed (skipping it here since it may contain project paths/metadata).

# `init` generates devcontainer.json referencing non-existent feature `ghcr.io/devcontainers/features/podman-in-podman`

Description

mxcli init generates a .devcontainer/devcontainer.json that references the dev container feature ghcr.io/devcontainers/features/podman-in-podman:1. This feature does not exist in the official [devcontainers/features](https://github.com/devcontainers/features) registry, so the dev container build fails when resolving features.

This reproduces on v0.11.0, which is currently the latest release, so it is not fixed by upgrading.

Environment

mxcli version	v0.11.0 (2026-05-21T18:04:46Z) (latest release)
Mendix version	11.8.0
OS	Windows 10 (build 26100)
Container runtime	Podman 5.8.2 (rootless), via Podman Desktop on WSL2
VS Code Dev Containers extension	0.459.1
Dev Containers CLI	0.86.1

Scenario

1. Run mxcli init on an existing Mendix project.
2. Open the project in VS Code and choose Dev Containers: Reopen in Container.
3. The build fails while resolving the podman-in-podman feature.

Generated config

The generated devcontainer.json contains:

"features": {
  "ghcr.io/devcontainers/features/podman-in-podman:1": {}
}

Experienced output

The dev container build fails while resolving the feature:

Could not resolve Feature manifest for 'ghcr.io/devcontainers/features/podman-in-podman:1'.
[httpOci] 403: Failed to fetch bearer token for 'ghcr.io':
  {"errors":[{"code":"DENIED","message":"requested access to the resource is denied"}]}
Error: Feature 'ghcr.io/devcontainers/features/podman-in-podman:1' could not be processed.

Expected output

A devcontainer.json referencing a feature that:

1. actually exists and is publicly pullable, and
2. provides a working container runtime inside the dev container for the PAD-based Mendix runtime + Postgres workflow,

while keeping the Podman host runtime (MXCLI_CONTAINER_CLI: "podman").

Diagnosis

The failure is not auth, network, or registry rate-limiting. Confirmed by testing anonymous bearer token requests directly against ghcr.io:

Scope	Result
devcontainers/features/git:pull	✅ returns a token
github/super-linter:pull	✅ returns a token
devcontainers/features/podman-in-podman:pull	❌ 403 DENIED

Additionally, the source path https://github.com/devcontainers/features/tree/main/src/podman-in-podman returns 404. The official devcontainers/features repository does not publish a podman-in-podman feature, so this reference can never resolve.

Question

What is the intended feature here?

• Should this be ghcr.io/devcontainers/features/docker-in-docker?
• A specific community-published podman-in-podman feature (which full path / namespace)?
• Or a custom setup via the Dockerfile / postCreateCommand instead of a feature?

Happy to test a fix. I can also provide a mxcli diag --bundle privately if needed (skipping it here since it may contain project paths/metadata).

[github-actions]

Issue Triage

Summary:
The mxcli init command creates a .devcontainer/devcontainer.json that references a non‑existent devcontainer feature (ghcr.io/devcontainers/features/podman-in-podman:1), causing the dev container build to fail.

Checklist for bug report completeness

Required info	Present?	Notes
mxcli version	❌	Not mentioned
Mendix version	❌	Not mentioned
Scenario (what the user was trying to do)	✅	mxcli init
Expected output	✅	A devcontainer config that resolves to a working feature
Experienced output (error message, etc.)	✅	Build fails with “Could not resolve Feature manifest … 403 DENIED”
AI bug report (mxcli diag --bundle or session log)	❌	Not provided

What’s missing:
Please provide the output of mxcli --version (or the commit/build info), the Mendix version of the project you’re working with, and, if possible, a diagnostic bundle from mxcli diag --bundle (or at least the relevant session log). This will help us reproduce the issue and verify any fix.

Thanks for reporting the problem! Once we have those details we can look into correcting the generated devcontainer configuration.

---

Automated triage via OpenRouter — workflow source