I2C inside a docker container

I am trying to use the i2c pins on a raspberry pi inside a docker container. I install all my modules using RUN but when I use the CMD to run my python program i get an error that says

Trackback (most recent call last):
file "test.py", line 124, in <module>
bus = smbus.SMBus(1)
IOError: [Errno 2] No such file or directory

If I run this on my raspberry pi and not in my container it works fine. But when I turn off my i2c pins on my raspberry pi it gives me the same error when running it. So I know it has to do with my i2c pins being activated. Does anyone know how to resolve this problem?

  • RestTemplate exchange call gives 503 error when running in Docker container at Kubernetes environment
  • NET I/O stats value missing inside GKE docker container
  • Using docker-compose to set containers timezones
  • Docker - issue command from one linked container to another
  • Secure server with Fail2ban and Docker
  • Docker run java app
  • high availability with docker swarm mode
  • How to use Nomad with Nvidia Docker?
  • Docker and Magento permission issues
  • Is it possible to start multiple docker daemons on the same machine
  • Is it possible running docker on big endian, arm32, linux=2.6.34?
  • MongoDB Docker Container on AWS ECS using EFS
  • One Solution collect form web for “I2C inside a docker container”

    As a security precaution, system devices are not exposed by default inside Docker containers. You can expose specific devices to your container using the --device option to docker run, as in:

    docker run --device /dev/i2c-0 --device /dev/i2c-1 myimage

    You can remove all restrictions with the --privileged flag:

    docker run --privileged myimage

    This will expose all of /dev to your container, and remove other restrictions as well (e.g., you will be able to change the network configuration in the container and mount new filesystems).

    Docker will be the best open platform for developers and sysadmins to build, ship, and run distributed applications.