Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add python 3.8 devcontainer #24

Merged
merged 1 commit into from
Oct 17, 2021
Merged

Conversation

ohthehugemanatee
Copy link
Contributor

Add a dev container definition, so visual studio code users automatically get an isolated environment in which to work.

I would go ahead and address #8 at the same time, but I'm not sure what system capabilities or devices we need to access to use the GPIO pins.

@jackw01 jackw01 merged commit 91af9fa into jackw01:master Oct 17, 2021
@Macleykun
Copy link

Add a dev container definition, so visual studio code users automatically get an isolated environment in which to work.

I would go ahead and address #8 at the same time, but I'm not sure what system capabilities or devices we need to access to use the GPIO pins.

Given this article: https://blog.hypriot.com/post/drive-neopixels-in-docker/
I believe this argument into run should make it work: docker run --privileged -d node-neopixel

@ohthehugemanatee
Copy link
Contributor Author

yes, it would work, but that's giving the container root privileges. Usual practice is to use --device, --cap-add, and --cap-drop flags to grant specific linux capabilities or devices. See docker documentation for the list of capabilities included by default and which ones you need to add manually. I just don't know the underlying python module well enough to know what capabilities/devices it needs to communicate with GPIO.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants