-
Notifications
You must be signed in to change notification settings - Fork 36
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
Issue when running containers through docker-compose up #64
Comments
Hi @aroop-biswal-vts - we're making some updates today to get this to a state where it will just come online. @meadej will be addressing. To answer your questions:
|
Hi @aroop-biswal-vts - thank you for bringing up these issues and for your patience. As @mchadwick-iqt mentioned above, we have placed some current development work under the main branch. For immediate use in the field, we have set-up a To use this branch, reference the Let us know if you have any further questions - they are greatly helpful in our work to build out documentation and improve stability. Thank you! |
We are attempting to run this project on this setup:
Software: Latest commit on main branch as of today.
OS - arm64 (2021-10-30 Bullseye)
Hardware - RaspberryPi4
When running docker-compose up, the images are successfully pulled. When running the images, however, we get some errors such as:
" ERROR:root:Unable to detect Coral boardFailed to load delegate from libedgetpu.so.1"
"cp: can't stat '/etc/letsencrypt/live/broker.mqtt.local/*.pem': No such file or directory
mqtt_1 | cat: can't open '/run/secrets/mqtt_user': No such file or directory
mqtt_1 | cat: can't open '/run/secrets/mqtt_pass': No such file or directory"
"axis-ptz_1 | raise ValueError('Invalid host.')
axis-ptz_1 | ValueError: Invalid host.
"
These errors raised a few questions:
We are a small group working on our summer internship research project and would greatly appreciate any guidance with getting this project set up. We would appreciate a point of contact and are open to receiving any communications through my email: [email protected].
Thank you for your time!
The text was updated successfully, but these errors were encountered: