Provide support in generic worker payload builder for docker worker properties
@petemoore is already working on this.
Since May 7, 2026.
Assessment
This issue has not been assessed yet.
Description
Taskgraph has worker-implementation-specific payload builders to convert abstract job definitions into taskcluster tasks. Payload builders declare a schema for the job properties they support. Jobs designed for Docker Worker contain properties that are currently not allowed by the Generic Worker payload builder, such as docker-image, allow-ptrace etc.
The d2g tool demonstrates that it is possible to transform a Docker Worker task definition into an equivalent Generic Worker task definition, and soon Generic Worker will perform this translation internally when running Docker Worker task payloads. However, task definitions designed for Docker Worker will not be able to use features that exist in Generic Worker only. Therefore it would be beneficial for the Generic Worker payload builder to support Docker Worker job definitions natively, and directly generate Generic Worker payloads that do not need to run through d2g inside of Generic Worker.
The d2g source code and command line utility can be used as a reference for understanding how to support Docker Worker features under Generic Worker. Furthermore, to validate that the updated payload builder works as anticipated, tests can be written that generate Docker Worker payloads from job definitions, transform them to Generic Worker using d2g, and compare the results to the same input job processed directly with the Generic Worker payload builder. The two should ideally be identical.
Note, the advantage of doing this, rather than having a transform step that runs d2g after generating a Docker Worker payload, is that eventually we can remove the Docker Worker payload builder altogether, and reduce the code footprint and complexity of dealing with multiple payload formats.
- Dominant language
- Python
- Stars
- 26
- Forks
- 55
- Avg merge
- 2d 6m
- Merged PRs (30d)
- 15
Contributor guide
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.
More from taskcluster/taskgraph
-
Dependency Dashboard Open
Difficulty 5/5 Over a week Newbie friendliness 20/100
taskcluster/taskgraph#952 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
taskcluster/taskgraph#915 ·
-
feature
Difficulty 3/5 1-2 days Newbie friendliness 35/100
taskcluster/taskgraph#911 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
taskcluster/taskgraph#882 ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
taskcluster/taskgraph#865 · 1 comment ·
All issues in taskcluster/taskgraph
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
zostera/django-bootstrap4#894 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
use-agent-os/agent-os#3276 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
zephyrproject-rtos/zephyr#119726 ·
-
area/auth bug comp/agent P3 platform/discord type/security
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
NousResearch/hermes-agent#117848 ·