# Installing Bell AVR Libraries

**URL:** <https://forum.theavr.org/t/installing-bell-avr-libraries/932>\
**Category:** AVR Drone Software\
**Created:** [October 2, 2024, 9:45pm UTC](https://forum.theavr.org/t/installing-bell-avr-libraries/932 "2024-10-02T21:45:24Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![CoastJRA](https://yyz1.discourse-cdn.com/flex007/user_avatar/forum.theavr.org/coastjra/32/352_2.png) [@CoastJRA](https://forum.theavr.org/u/CoastJRA)\
**Post date:** [October 2, 2024, 9:45pm UTC](https://forum.theavr.org/t/installing-bell-avr-libraries/932/1 "2024-10-02T21:45:24Z")

</div>

When trying to run the sandbox.py file in VS Code, we get this error:  
Traceback (most recent call last):  
File “/home/avr/AVR-2022/VMC/sandbox/sandbox.py”, line 5, in   
from bell.avr.mqtt.client import MQTTModule  
ModuleNotFoundError: No module named ‘bell’

We have trying installing the Bell AVR Libraries with “pip install bell-avr-libraries” but we get this error:  
ERROR: Could not find a version that satisfies the requirement bell-avr-libraries (from versions: none)  
ERROR: No matching distribution found for bell-avr-libraries

---

<div class="post-metadata">

**Author:** ![Jurassic\_001](https://yyz1.discourse-cdn.com/flex007/user_avatar/forum.theavr.org/jurassic_001/32/458_2.png) [@Jurassic\_001](https://forum.theavr.org/u/Jurassic_001)\
**Post date:** [October 3, 2024, 6:11pm UTC](https://forum.theavr.org/t/installing-bell-avr-libraries/932/2 "2024-10-03T18:11:48Z")

</div>

I think your issue is that you are running the sandbox file directly from VSCode, instead of as a docker container. The AVR software is not intended to be run as a standalone Python file. I would take a look at the [Docker](https://the-avr.github.io/AVR-2022/autonomy-and-beyond/docker/) section of the AVR build guide. If you have any questions, feel free to ask me.

However, if you are running the sandbox as a docker container, then I would recommend that you update your software using `setup.py` and re-run it. Also, if you could provide all of your docker container logs (the messages that start printing after you use `start.py run`) that could help in diagnosing the issue.