Error with bridge.sh using Apollo 5.0

[WhoAmI-kai]

I've been trying to run the simulator with Apollo 5.0 and when I execute bridge.sh, I get the following error message: scripts/bridge.sh: line 6: bazel-bin/cyber/bridge/cyber_bridge: No such file or directory

Any ideas on what I'm doing wrong? One error message I also see in the previous step (I don't know if it's related or not) is that when I execute bootstrap.sh, it says:

nohup: appending output to 'nohup.out'
nohup: appending output to 'nohup.out'
Could not launch module monitor. Is it already built?
nohup: appending output to 'nohup.out'
Launched module dreamview.
Failed to start Dreamview. Please check /apollo/data/log or /apollo/data/core for more information

[EricBoiseLGSVL]

@revati-naik @hadiTab any idea?

[revati-naik]

@WhoAmI-kai Please follow the instructions provided here to build the Apollo 5.0 container. After you enter the container, please build Apollo using ./apollo.sh build_opt_gpu before running bootstrap.sh

[WhoAmI-kai]

I have used./apollo.sh build_opt_gpu before running bootstrap.sh, but only the first time it can run。 When I restart the container or restart the machine and ran bootstrap.sh, I get the following error message:

nohup: appending output to 'nohup.out'
nohup: appending output to 'nohup.out'
Could not launch module monitor. Is it already built?
nohup: appending output to 'nohup.out'
Launched module dreamview.
Failed to start Dreamview. Please check /apollo/data/log or /apollo/data/core for more information

Then, when I executed bridge.sh, I get the following error message: scripts/bridge.sh: line 6: bazel-bin/cyber/bridge/cyber_bridge: No such file or directory

[lemketron]

Before you can run bootstrap or bridge, you must first start and enter the container as you did before building.

See here and here.

[WhoAmI-kai]

Thank you for your reply.

I have started and entered the container as I did before building, then I get that error when I run bootstrap and bridge

发自我的iPhone

------------------ Original ------------------ From: Steve Lemke @.> Date: Thu,Aug 26,2021 2:20 AM To: lgsvl/simulator @.> Cc: WhoAmI-kai @.>, Mention @.> Subject: Re: [lgsvl/simulator] Error with bridge.sh using Apollo 5.0 (#1707)

Before you can run bootstrap or bridge, you must first start and enter the container as you did before building.

See here and here.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android.

[lemketron]

I have started and entered the container as I did before building, then I get that error when I run bootstrap and bridge

Are you sure the Apollo 5.0 build completed successfully without any errors? It's hard to say why it's not launching for you but it appears that something did not build correctly.

Apollo 5.0 is also getting pretty old. I would suggest looking at newer upstream Apollo which includes support for SVL Simulator (6.0 or master). You can find that documented here.

[WhoAmI-kai]

I have tried to rebuild Apollo many times, I'm sure the Apollo 5.0 build completed successfully without any error. For some reason I have to choose Apollo 5.0 with LGSVL.

发自我的iPhone

------------------ Original ------------------ From: Steve Lemke @.> Date: Thu,Aug 26,2021 2:27 AM To: lgsvl/simulator @.> Cc: WhoAmI-kai @.>, Mention @.> Subject: Re: [lgsvl/simulator] Error with bridge.sh using Apollo 5.0 (#1707)

I have started and entered the container as I did before building, then I get that error when I run bootstrap and bridge

Are you sure the Apollo 5.0 build completed successfully without any errors? It's hard to say why it's not launching for you but it appears that something did not build correctly.

Apollo 5.0 is also getting pretty old. I would suggest looking at newer upstream Apollo which includes support for SVL Simulator (6.0 or master). You can find that documented here.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android.

[revati-naik]

@WhoAmI-kai Could you please share the screenshot of the terminal which is running Apollo container. I would want to check the image on which the conatiner is built. It can be dev or runtime based on which file you use to start the container.

[WhoAmI-kai]

[revati-naik]

@WhoAmI-kai As fasr as what I have noticed is that while using a dev container, we need to build the container everytime we enter the container. We test with the runtime container and do not see this issue. If it suits your need, woudl you mind testing with the runtime container. Could you please follow the steps given here?