-
Notifications
You must be signed in to change notification settings - Fork 87
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
Core: Compose: compose.yml does not build development environment #3030
Comments
Ping @voorloopnul |
Hello Andrew, you are right, the correct image is: public.ecr.aws/blueos/bcloud-agent |
This is the issue I am receiving. I see you made a PR so I can try that as well.
|
@andrewkwolek can you try the latest master ? |
@patrickelectric sorry for the delayed reply. I pulled and merged the latest master and am still seeing the same error in blueos-cloud-telemetry Seeing this error: |
@patrickelectric I was able to get both images running on my machine! Your fix worked. I realized I didn't pull the updated docker image, I just pulled the code to my local git repo. I am seeing the following error in cloud-telemetry: I have a BlueROV2 arriving in a few days so I should be able to test on a real robot shortly. Thanks! |
I'll look into it, but of you are not using BlueOS cloud features you should be fine. |
@andrewkwolek I just checked now and the error is not there, did it appears only once ? |
Hey @patrickelectric. It continues to appear every 20 seconds as it can not find the bag service. Should I be running QGroundControl or some other process in addition to BlueOS? Maybe I've missed something. |
Hey @patrickelectric I am unable to access any of the services through my localhost when I run the container. It does not show any ports being exposed to my system. Am I missing something? This is the full log when I spin up the container.
|
Hi @patrickelectric. I figured it out! Long story short I had another process running on port 80 which is why cloud telemetry couldn't connect, and then for whatever reason |
Having a service running at port 80 explains why. network_mode host should just work, if you are running inside a VM or something like it may explain. There are also some problems in macos related to network_mode host. That's why we have all the ports mapped |
Closing for now, be free to reopen. |
I tried using docker to build the development environment but found that the cloud-telemetry image does not exist. The current image in the master branch is
cloud-telemetry: image: public.ecr.aws/h4c9p1o0/blueos-cloud-agent-dev
.I found an active image in AWS ECR called
public.ecr.aws/blueos/bcloud-agent
which allowed me to successfully pull and run the environment. However, I received an exception in cloud-telemetry about non-existent files.Is
public.ecr.aws/blueos/bcloud-agent
the correct image for cloud-telemetry or does it no longer exist?Thanks!
The text was updated successfully, but these errors were encountered: