interactive docker-worker tasks don't start the system dbus daemon
Categories
(Firefox Build System :: Task Configuration, defect, P3)
Tracking
(firefox135 fixed)
| Tracking | Status | |
|---|---|---|
| firefox135 | --- | fixed |
People
(Reporter: jcristau, Assigned: jcristau)
Details
Attachments
(1 file)
The ubuntu*-test dockerfiles set an entry point for the image:
https://searchfox.org/mozilla-central/rev/55837bbe3e47f9b4fa91ef83a44b53823626f01d/taskcluster/docker/ubuntu1804-test/Dockerfile#83
That causes the dbus system bus to get started before run-task itself, making it available to the task.
When using the "interactive" taskcluster feature to run tasks, however, docker-worker overrides the entrypoint to start its interactive_wrapper_run.sh (https://github.com/taskcluster/taskcluster/blob/930d5517c4c0a11582e01eae74d2b3c1b037bb02/workers/docker-worker/src/task.js#L445-L456); in theory that should run the old entrypoint, but in practice that's not what we're seeing (either due to a bug or a too-old docker-worker or ...).
| Assignee | ||
Comment 1•11 months ago
|
||
Comment 2•11 months ago
|
||
The severity field is not set for this bug.
:bhearsum, could you have a look please?
For more information, please visit BugBot documentation.
| Assignee | ||
Updated•11 months ago
|
Comment 3•11 months ago
|
||
Not sure this should be assigned to you, Julien, but you are probably best positioned to triage?
| Assignee | ||
Comment 4•11 months ago
|
||
Yeah I guess I'll take this. Interactive tasks in general are in dire need of TLC, but since I've got a workaround for this I might go ahead and land it.
Updated•10 months ago
|
Updated•10 months ago
|
Description
•