-
Suggestion
-
Resolution: Unresolved
Please add a setting in bitbucket-pipelines.yml to allow docker images to be started with the "--privileged" flag.
Use: privileged flag allows network configuration needed for VPN connection used for deployment to dev/qa server.
- is cloned from
-
- Closed
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[BCLOUD-21589] Allow Docker Image to access SUB devices
I would also like to see this feature. Anybody know if there is a way to do this currently?
Any update on this? Being able to access USB devices is vital for embedded testing on self-hosted runners.
This would be a great addition for self hosted runners. Would simplify many hardware in the loop test cases. Workarounds using ssh or otherwise are awful.
Atlassian, any news. This is trivial to implement. Just an extra parameter to docker start
It would be really handy to be able to access the USB devices of self-hosted runners. Thumbs up!
Feature request:
Accessing host USB devices is needed for running tests that involve any peripherals connected via USB.
That requires either privileged mode or starting a container with --device=/dev/ttyUSB0:/dev/ttyUSB0
8ed621fe5b2e I have still not heard/seen anything regarding actually being able to use USB devices from the self-hosted docker runner.
To bypass this issue, I currently use the self-hosted Linux shell runner (aka. 'linux.shell'). That allows me to run jobs as the normal user of the computer I use. This is not very nice though, since a bad job can mess up the whole computer setup potentially. Also, if you don't run the shell-runner as sudo (which I don't recommend), you may need to add your user to dialout or some other group with access to the USB devices, eg. with
sudo usermod -a -G dialout <my-user>.