Give Docker container access to first USB device by default - closes #3204 #3221
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Member
Author
|
Going to close this now while we continue to evaluate balenaOS. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Giving add-ons access to all serial ports without also giving them access to a lot of other stuff they don't need is going to be tricky. Ideally add-ons would have access to all serial devices and support hotplug to dynamically map them into the Docker container, but that is going to be tricky.
How about as a starting point we just hard code access to
/dev/ttyUSB0by default in docker-compose? That should hopefully allow add-ons access to the first serial device connected via USB (e.g. a Zigbee or Z-Wave dongle), which in many cases will be all the user needs. Users can manually add and remove devices in docker-compose.yml, or manually start Docker with their own settings.Is that reasonable?
Closes #3204 (kind of).