Proxy issue with ide-jupyter-python3 addon about sas-container-recipes

[g8sman]

You are correct that we need to update the documentation if you are trying to add on the layer outside of using the root level build.sh script. You would need to run the docker build process twice using each of the Docker files that are available. The logic looks like it is not as forgiving as it needs to be in the Dockerfile_http. We will probably need to introduce a new build argument to indicate if we are supporting a single or multiple container to make this work. Assuming that you are trying to create a single container, you could do something like:

docker build --file Dockerfile --build-arg BASEIMAGE=viya-single-container --build-arg BASETAG=latest  . --tag viya-single-container:jpy3
docker build --file Dockerfile --build-arg BASEIMAGE=viya-single-container --build-arg BASETAG=jpy3  . --tag svc-ide-jupyter-python3

If you are using the multi-container flow, this proxy.conf file needs to be added to the httpproxy Docker image.

[githje]

Thanks @g8sman! Yes, I'm not using the build.sh script - should have mentioned that before. I think there's a typo in your explanation. The first build should be using Dockerfile_http, right?

This works for me:

docker build --file Dockerfile_http --build-arg BASEIMAGE=viya-single-container --build-arg BASETAG=latest  . --tag viya-single-container:jpy3
docker build --file Dockerfile --build-arg BASEIMAGE=viya-single-container --build-arg BASETAG=jpy3  . --tag svc-ide-jupyter-python3

Then I headed over to addons/auth-demo for example and did

docker build --file Dockerfile --build-arg BASEIMAGE=svc-ide-jupyter-python3 --build-arg BASETAG=latest  . --tag svc-auth-demo

Thanks for the explanation, I'm fine with that.