TimeToogo / TimeToogo/tunshell
Feature request: locally generated session & key
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 818
- Forks
- 58
- PR merge metrics
- No merged PRs in 30d
Description
I have a use-case where I am trying to debug CI pipelines that build Docker containers. The Docker containers are being built simultaneously as arm64 as well as x86 using BuildKit.
To that end, adding a tunshell command to the build script ends up running the command twice: once in an arm64 environment and one in an x86 environment. This causes one of the commands to fail with "Error occurred: Connection has already been joined by another host". This kills the BuildKit command.
Is it possible to build a feature where the session & key are generated on demand by the client, with these parameters printed to stdout?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the tunshell client command and its session/key handling. Trace how concurrent Docker BuildKit invocations currently join a session, then define the command output needed for independently generated values. Done means parallel arm64 and x86 builds can run without a duplicate-connection failure and the generated session and key are printed to stdout.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, rust
- Domain
- build-system, cli, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100