# Access /dev/serial/by-id/\<device\> within a container

**URL:** <https://forums.balena.io/t/access-dev-serial-by-id-device-within-a-container/370214>\
**Category:** balenaEngine\
**Tags:** docker, raspberrypi4\
**Created:** [March 30, 2024, 9:41pm UTC](https://forums.balena.io/t/access-dev-serial-by-id-device-within-a-container/370214 "2024-03-30T21:41:16Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![bverhagen](https://avatars.discourse-cdn.com/v4/letter/b/278dde/32.png) [@bverhagen](https://forums.balena.io/u/bverhagen)\
**Post date:** [March 30, 2024, 9:41pm UTC](https://forums.balena.io/t/access-dev-serial-by-id-device-within-a-container/370214/1 "2024-03-30T21:41:16Z")

</div>

For my use case, I attach multiple USB CDC modem devices to a raspberry pi 4 running Balena OS. When logging into the host system, I can nicely use the `/dev/serial/by-id/<unique device id>` symlink to consistently access the same device over and over.

However, in the deployed containers (based on `balenalib/%%BALENA_MACHINE_NAME%%-alpine`), `/dev` is mounted in the containers and connecting to e.g. `/dev/ttyACM0` works flawlessly. However, in the container, I am not able to find the `/dev/serial/by-id` folder.

Is there a way to enable this or achieve a similar consistent access from within the alpine container?
