Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Podman: unable to upgrade to tcp, received 500

Open
#299 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
52/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Active
Tech stack
docker, go
Domain
cli

Research direction

Start at the crossplane composition render entry point and trace the internal render-in-Docker path that attaches to the function container. Reproduce with a rootful Podman machine and compare the failing container-attach behavior with the working 2.2.0 release; done means rendering succeeds on the reported Podman setup.

Written by the indexing model from the issue text.

Description

bug
What happened?

Since the update to 2.3.0 the crossplane cli is not working anymore in my setup.
Version 2.2.0 is running without any issues.
I am using podman with rootful setup.

How can we reproduce it?
  • Install podman 6.1.0
  • Create rootful machine
  • Try "crossplane composition render"
  • Fail with:
2026-08-21T18:28:39+02:00       DEBUG   Function container reachable on network {"network": "crossplane-render-9jnm6ht7", "address": "hardcore_hodgkin:9443"}
2026-08-21T18:28:39+02:00       DEBUG   Running crossplane internal render in Docker    {"image": "xpkg.crossplane.io/crossplane/crossplane:stable", "network": "crossplane-render-9jnm6ht7"}
crossplane: error: cannot render composite resource: crossplane internal render in Docker returned error with output: : failed to attach to container: unable to upgrade to tcp, received 500
What environment did it happen in?
  • Crossplane CLI version: 2.3.0 -> 2.5.0
  • Platform (e.g., linux/amd64): macos arm64
  • Crossplane version (if applicable):
Dominant language
Go
Stars
19
Forks
31
Avg merge
2d 15h
Merged PRs (30d)
53

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from crossplane/cli

All issues in crossplane/cli

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.