Describe the bug
There seems to be an issue with building container image with the sas-container-recipes.
To Reproduce
Steps to reproduce the behavior:
If the container was built before and the Dockerfile is unchanged the docker build command will skip the build steps and use cached data to create the image. If this case apply to you, you can add the
--no-cache flag to the docker build command in the build.sh script:
Command
Run time ./build.sh --type single --addons "auth-demo" --zip ~/recipes/sas-container-recipes/SAS_Viya_deployment_data.zip
Scroll to the
Step 5/20 : RUN go get -x -u gopkg.in/yaml.v2 github.com/docker/docker/api/types github.com/docker/docker/client
See error
The command '/bin/sh -c go get -x -u gopkg.in/yaml.v2 github.com/docker/docker/api/types github.com/docker/docker/client' returned a non-zero code: 2
Expected behavior
The github.com/docker/docker/client source in the go get command doesn't seem to work.
I did build this image few weeks ago and the build was successful.
I tried to built it on 2 environments - Centos and openstack rhel cluster.
Environment:
1st OS: CentOS Linux 7 (Core) , Docker version 19.03.8
2nd OS: Red Hat Enterprise Linux Server 7.7 (Maipo) , Docker version 1.13.1
Describe the bug There seems to be an issue with building container image with the sas-container-recipes.
To Reproduce Steps to reproduce the behavior:
time ./build.sh --type single --addons "auth-demo" --zip ~/recipes/sas-container-recipes/SAS_Viya_deployment_data.zip
Expected behavior The github.com/docker/docker/client source in the go get command doesn't seem to work. I did build this image few weeks ago and the build was successful. I tried to built it on 2 environments - Centos and openstack rhel cluster.
Environment: