You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 30, 2022. It is now read-only.
We are attempting to perform a SAS containerized full deployment using a RHEL 7.8 base image. When running the build script (using the command below), it gives an error.
Build command
./build.sh --type full --base-image --base-tag latest --zip ../SAS_Viya_deployment_data.zip --docker-registry-url --docker-namespace sas --addons "auth-sssd access-odbc"
Errors
unable to sync file '/var/lib/dpkg/tmp.ci//control': Input/output error
dpkg: error processing archive /tmp/apt-dpkg-install-qLupvE/68-python3-selinux_2.8-1+b1_amd64.deb (--unpack):
unable to sync file '/var/lib/dpkg/tmp.ci//md5sums': Input/output error
dpkg: error processing archive /tmp/apt-dpkg-install-qLupvE/69-python3-xmltodict_0.11.0-2_all.deb (--unpack):
unable to sync file '/var/lib/dpkg/tmp.ci//control': Input/output error
dpkg: error processing archive /tmp/apt-dpkg-install-qLupvE/70-python3-winrm_0.3.0-2_all.deb (--unpack):
unable to sync file '/var/lib/dpkg/tmp.ci//control': Input/output error
dpkg: error: unable to sync new file '/var/lib/dpkg/status-new': Input/output error
E: Sub-process /usr/bin/dpkg returned an error code (2)
Although we have specified a RHEL image as an argument in the command line to run the build script, it appears to be pulling debian packages. Please advise.
The text was updated successfully, but these errors were encountered:
• The container recipes start a build container and from within that container it starts to build the viya docker images
• That build container is based on the GOLANG image. This is a based on a debian OS that you are seeing in the script. That’s where the error message is coming from. It fails to build the build container
• It seems to fail at updating the packages on the OS. To be precise it fails at this step: https://github.com/sassoftware/sas-container-recipes/blob/master/Dockerfile#L8
• The base image provided by this customer will be used as a base image for the VIYA docker images
It is likely that that web proxy is blocking internet traffic from there docker daemon. So the build of the container fails because it is not able to download the required packages. It may take some modification of the golang container to start the build process correctly.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Based on information provided in the link below:
https://github.com/sassoftware/sas-container-recipes/wiki/Build-and-Run-SAS-Viya-Multiple-Containers
We are attempting to perform a SAS containerized full deployment using a RHEL 7.8 base image. When running the build script (using the command below), it gives an error.
Build command
./build.sh --type full --base-image --base-tag latest --zip ../SAS_Viya_deployment_data.zip --docker-registry-url --docker-namespace sas --addons "auth-sssd access-odbc"
Errors
unable to sync file '/var/lib/dpkg/tmp.ci//control': Input/output error
dpkg: error processing archive /tmp/apt-dpkg-install-qLupvE/68-python3-selinux_2.8-1+b1_amd64.deb (--unpack):
unable to sync file '/var/lib/dpkg/tmp.ci//md5sums': Input/output error
dpkg: error processing archive /tmp/apt-dpkg-install-qLupvE/69-python3-xmltodict_0.11.0-2_all.deb (--unpack):
unable to sync file '/var/lib/dpkg/tmp.ci//control': Input/output error
dpkg: error processing archive /tmp/apt-dpkg-install-qLupvE/70-python3-winrm_0.3.0-2_all.deb (--unpack):
unable to sync file '/var/lib/dpkg/tmp.ci//control': Input/output error
dpkg: error: unable to sync new file '/var/lib/dpkg/status-new': Input/output error
E: Sub-process /usr/bin/dpkg returned an error code (2)
Although we have specified a RHEL image as an argument in the command line to run the build script, it appears to be pulling debian packages. Please advise.
The text was updated successfully, but these errors were encountered: