Podman compatibility

Open
#68 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Quiet
Tech stack
node.js, typescript
Domain
devops

Research direction

Reproduce the failure in ContainerExec or ExecStart using Podman over both the socket and TCP address, then inspect undici's lib/api/api-upgrade.js at the referenced commit. Determine whether the bad upgrade comes from an unsupported Podman response or from this library's request handling; done means an agreed compatibility change or a documented support limitation with a reproducible test case.

Written by the indexing model from the issue text.

Description

Trying to use this library with podman, I get a "bad upgrade" , coming from this code in undici, when trying to use ContainerExec / ExecStart .

Pulling images and creating/starting containers works just fine with podman otherwise.

Also tried to connect to podman via both the socket and the tcp address, but that didn't seem to make a difference.

Is podman supported ? If not, would that be a goal for this library ?

Any other clues as to what I might be doing wrong ?

Dominant language
TypeScript
Stars
107
Forks
12
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

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 docker/node-sdk

All issues in docker/node-sdk

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.