Closed Bug 1639713 Opened 5 years ago Closed 5 years ago

docker-worker errors with `/dev/shm: not a device node` when hostSharedMemory device enabled

Categories

(Taskcluster :: Operations and Service Requests, defect)

Product:
Taskcluster
Component:
Operations and Service Requests
Platform:
Unspecified
Linux
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: truber, Unassigned)

References

Details

In my task definition I have:

scopes:
 - docker-worker:capability:device:hostSharedMemory
payload
  capabilities:
    devices:
      hostSharedMemory: true
  ...
...

Executing this task results in the following error:

[taskcluster 2020-05-20 13:14:29.237Z] === Task Starting ===
[taskcluster:error] Failure to properly start execution environment.
[taskcluster:error] (HTTP code 500) server error - error gathering device information while adding custom device "/dev/shm": not a device node 
[taskcluster 2020-05-20 13:14:33.291Z] === Task Finished ===

An example task is here: https://community-tc.services.mozilla.com/tasks/Vg182WlERGazGy5NM61q5Q

The intent of this feature is to mount /dev/shm from the host into the container because we often run multiple instances of ASAN firefox in a single container.

This topic just came up in bug 1638652 comment 19. There should be a way to run Firefox in Docker without having to disable e10s.

See Also: → 1638652
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.