Docker build fails if no_proxy setting contains spaces

[yogeshmpandey]

Tried to build the image using

./docker/build.sh

But, getting the issue below:-

[whbruce]

This is probably due to a space in your NO_PROXY setting. Run the following to track down the problem.

$ grep localhost docker/openvino_base_environment.txt
no_proxy=localhost,127.0.0.1
NO_PROXY=127.0.0.1, localhost

If you see space in either of these values (as in NO_PROXY setting), the build will break with the error you reported. Check your environment and docker proxy configuration for such spaces.

[yogeshmpandey]

Thanks, I was able to run it after making the changes. However since I am using a VM, I am getting this issue after running the run.sh command, do we have any fixes for this.

[nnshah1]

@yogeshmpandey What underlying hardware are you using? Based on this similar issue (also running from within a VM) opencv/opencv#18932 it looks like you may need to rebuild opencv / openvino with those options disabled.

I would suggest rebuilding the base openvino image using:
https://github.com/openvinotoolkit/docker_ci and
ttps://github.com/openvinotoolkit/docker_ci/blob/master/get-started.md

You'll want to select 'data_runtime' as the type.

Once you've build a openvino data_runtime base image for your HW config, you can use that as a base image for VA Serving:

https://github.com/intel/video-analytics-serving/blob/master/docs/building_video_analytics_serving.md

https://github.com/intel/video-analytics-serving/blob/master/docs/build_script_reference.md

Let us know if that works -

[yogeshmpandey]

Thanks, a lot. It worked.