topic Re: SAS Viya 3.4 for Containers: error in deployment in Administration and Deployment

SAS Viya 3.4 for Containers: error in deployment

AndreasMenrath — Mon, 08 Oct 2018 14:59:26 GMT

Hello everyone,

i am trying to create a docker container from the SAS repository.

The documentation is found at: http://support.sas.com/rnd/containers/index.html

I am trying the way 1 "Use the Docker Image approach"

Therefore i use this deployment guide:

https://documentation.sas.com/api/docsets/dplyml0phy0dkr/3.4/content/dplyml0phy0dkr.pdf?locale=de#nameddest=p03lavfsdxc79tn1x2nd84i0wujx

I am stuck at page 14 when i run this command because it has no output:

mirrormgr list remote docker tags --deployment-data $(pwd)/SAS_Viya_deployment_data.zip --latest

I fullfill all requirements and have a valid SAS Viya 3.4 licence.

So here are my questions:

are there any docker images available at all?

do i need an extra licence if i want to deploy Viya 3.4 in a docker container?

I hope that the SAS experts here can help me to figure out what is going wrong.

Best regards

Andreas Menrath

Re: SAS Viya 3.4 for Containers: error in deployment

SimonDawson — Tue, 09 Oct 2018 00:29:34 GMT

The mirrormgr utility should write a log in $HOME\.local\share\mirrormgr\mirrormgr.log
Does this give any insight into the hang you are seeing?

Re: SAS Viya 3.4 for Containers: error in deployment

AndreasMenrath — Tue, 09 Oct 2018 06:55:15 GMT

the log file exists, but is completely empty with a file size of 0 Bytes

Re: SAS Viya 3.4 for Containers: error in deployment

SimonDawson — Tue, 09 Oct 2018 11:19:19 GMT

Can you confirm my understanding of the issue is correct. You execute the mirrormgr and it hangs, you don't get your terminal back?

If my understanding is correct you might try with a -d command line switch to enable debug logging. This utility obviously connects to SAS servers to query some things does the host you are running this on have access to the Internet?

Re: SAS Viya 3.4 for Containers: error in deployment

AndreasMenrath — Tue, 09 Oct 2018 12:33:29 GMT

i get the terminal back after a second. The output of the mirror manager to stdoud is just empty.

With the --debug flag i see more output, but not what i expect:

evaulating path: licenses/SASViyaV0300_9C1458_Linux_x86-64.txt
evaulating path: licenses/SASViyaV0300_9C1458_70223818_Linux_x86-64.jwt
evaulating path: ca-certificates/SAS_CA_Certificate.pem
parsing ca cert
evaulating path: ca-certificates/SAS_CA_Certificate.p7b
evaulating path: entitlement-certificates/entitlement_certificate.pem
parsing client cert
evaulating path: entitlement-certificates/entitlement_certificate.pfx
evaulating path: order.oom
attempting to parse repos/shipped/connect/100/connect-100-x64_suse_linux_12-yum
attempting to parse repos/shipped/connect/104/connect-104-x64_redhat_linux_6-yum
attempting to parse repos/shipped/dmdatap/100/dmdatap-100-x64_suse_linux_12-yum
attempting to parse repos/shipped/dmdatap/104/dmdatap-104-x64_redhat_linux_6-yum
attempting to parse repos/shipped/dmdq/100/dmdq-100-x64_suse_linux_12-yum
attempting to parse repos/shipped/dmdq/104/dmdq-104-x64_redhat_linux_6-yum
attempting to parse repos/shipped/esp/100/esp-100-x64_suse_linux_12-yum
attempting to parse repos/shipped/esp/104/esp-104-x64_redhat_linux_6-yum
attempting to parse repos/shipped/forecast/100/forecast-100-x64_suse_linux_12-yum
attempting to parse repos/shipped/forecast/104/forecast-104-x64_redhat_linux_6-yum
attempting to parse repos/shipped/hive/100/hive-100-x64_suse_linux_12-yum
attempting to parse repos/shipped/hive/104/hive-104-x64_redhat_linux_6-yum
attempting to parse repos/shipped/impala/100/impala-100-x64_suse_linux_12-yum
attempting to parse repos/shipped/impala/104/impala-104-x64_redhat_linux_6-yum
attempting to parse repos/shipped/indbhive/100/indbhive-100-x64_suse_linux_12-yum
attempting to parse repos/shipped/indbhive/104/indbhive-104-x64_redhat_linux_6-yum
attempting to parse repos/shipped/mlrning/100/mlrning-100-x64_suse_linux_12-yum
attempting to parse repos/shipped/mlrning/104/mlrning-104-x64_redhat_linux_6-yum
attempting to parse repos/shipped/modelmgr/100/modelmgr-100-x64_suse_linux_12-yum
attempting to parse repos/shipped/modelmgr/104/modelmgr-104-x64_redhat_linux_6-yum
attempting to parse repos/shipped/odbc/100/odbc-100-x64_suse_linux_12-yum
attempting to parse repos/shipped/odbc/104/odbc-104-x64_redhat_linux_6-yum
attempting to parse repos/shipped/opt/100/opt-100-x64_suse_linux_12-yum
attempting to parse repos/shipped/opt/104/opt-104-x64_redhat_linux_6-yum
attempting to parse repos/shipped/oracle/100/oracle-100-x64_suse_linux_12-yum
attempting to parse repos/shipped/oracle/104/oracle-104-x64_redhat_linux_6-yum
attempting to parse repos/shipped/pcfile/100/pcfile-100-x64_suse_linux_12-yum
attempting to parse repos/shipped/pcfile/104/pcfile-104-x64_redhat_linux_6-yum
attempting to parse repos/shipped/postgres/100/postgres-100-x64_suse_linux_12-yum
attempting to parse repos/shipped/postgres/104/postgres-104-x64_redhat_linux_6-yum
attempting to parse repos/shipped/statviya/100/statviya-100-x64_suse_linux_12-yum
attempting to parse repos/shipped/statviya/104/statviya-104-x64_redhat_linux_6-yum
attempting to parse repos/shipped/teradata/100/teradata-100-x64_suse_linux_12-yum
attempting to parse repos/shipped/teradata/104/teradata-104-x64_redhat_linux_6-yum
attempting to parse repos/shipped/txtminger/100/txtminger-100-x64_suse_linux_12-yum
attempting to parse repos/shipped/txtminger/104/txtminger-104-x64_redhat_linux_6-yum
attempting to parse repos/shipped/va/100/va-100-x64_suse_linux_12-yum
attempting to parse repos/shipped/va/104/va-104-x64_redhat_linux_6-yum
attempting to parse repos/shipped/vtxtan/100/vtxtan-100-x64_suse_linux_12-yum
attempting to parse repos/shipped/vtxtan/104/vtxtan-104-x64_redhat_linux_6-yum
attempting to parse sasmd/shipped/connect/100/connect-100-x64_suse_linux_12-yumsasmd
attempting to parse sasmd/shipped/connect/104/connect-104-x64_redhat_linux_6-yumsasmd
attempting to parse sasmd/shipped/dmdatap/100/dmdatap-100-x64_suse_linux_12-yumsasmd
attempting to parse sasmd/shipped/dmdatap/104/dmdatap-104-x64_redhat_linux_6-yumsasmd
attempting to parse sasmd/shipped/dmdq/100/dmdq-100-x64_suse_linux_12-yumsasmd
attempting to parse sasmd/shipped/dmdq/104/dmdq-104-x64_redhat_linux_6-yumsasmd
attempting to parse sasmd/shipped/esp/100/esp-100-x64_suse_linux_12-yumsasmd
attempting to parse sasmd/shipped/esp/104/esp-104-x64_redhat_linux_6-yumsasmd
attempting to parse sasmd/shipped/forecast/100/forecast-100-x64_suse_linux_12-yumsasmd
attempting to parse sasmd/shipped/forecast/104/forecast-104-x64_redhat_linux_6-yumsasmd
attempting to parse sasmd/shipped/hive/100/hive-100-x64_suse_linux_12-yumsasmd
attempting to parse sasmd/shipped/hive/104/hive-104-x64_redhat_linux_6-yumsasmd
attempting to parse sasmd/shipped/impala/100/impala-100-x64_suse_linux_12-yumsasmd
attempting to parse sasmd/shipped/impala/104/impala-104-x64_redhat_linux_6-yumsasmd
attempting to parse sasmd/shipped/indbhive/100/indbhive-100-x64_suse_linux_12-yumsasmd
attempting to parse sasmd/shipped/indbhive/104/indbhive-104-x64_redhat_linux_6-yumsasmd
attempting to parse sasmd/shipped/mlrning/100/mlrning-100-x64_suse_linux_12-yumsasmd
attempting to parse sasmd/shipped/mlrning/104/mlrning-104-x64_redhat_linux_6-yumsasmd
attempting to parse sasmd/shipped/modelmgr/100/modelmgr-100-x64_suse_linux_12-yumsasmd
attempting to parse sasmd/shipped/modelmgr/104/modelmgr-104-x64_redhat_linux_6-yumsasmd
attempting to parse sasmd/shipped/odbc/100/odbc-100-x64_suse_linux_12-yumsasmd
attempting to parse sasmd/shipped/odbc/104/odbc-104-x64_redhat_linux_6-yumsasmd
attempting to parse sasmd/shipped/opt/100/opt-100-x64_suse_linux_12-yumsasmd
attempting to parse sasmd/shipped/opt/104/opt-104-x64_redhat_linux_6-yumsasmd
attempting to parse sasmd/shipped/oracle/100/oracle-100-x64_suse_linux_12-yumsasmd
attempting to parse sasmd/shipped/oracle/104/oracle-104-x64_redhat_linux_6-yumsasmd
attempting to parse sasmd/shipped/pcfile/100/pcfile-100-x64_suse_linux_12-yumsasmd
attempting to parse sasmd/shipped/pcfile/104/pcfile-104-x64_redhat_linux_6-yumsasmd
attempting to parse sasmd/shipped/postgres/100/postgres-100-x64_suse_linux_12-yumsasmd
attempting to parse sasmd/shipped/postgres/104/postgres-104-x64_redhat_linux_6-yumsasmd
attempting to parse sasmd/shipped/statviya/100/statviya-100-x64_suse_linux_12-yumsasmd
attempting to parse sasmd/shipped/statviya/104/statviya-104-x64_redhat_linux_6-yumsasmd
attempting to parse sasmd/shipped/teradata/100/teradata-100-x64_suse_linux_12-yumsasmd
attempting to parse sasmd/shipped/teradata/104/teradata-104-x64_redhat_linux_6-yumsasmd
attempting to parse sasmd/shipped/txtminger/100/txtminger-100-x64_suse_linux_12-yumsasmd
attempting to parse sasmd/shipped/txtminger/104/txtminger-104-x64_redhat_linux_6-yumsasmd
attempting to parse sasmd/shipped/va/100/va-100-x64_suse_linux_12-yumsasmd
attempting to parse sasmd/shipped/va/104/va-104-x64_redhat_linux_6-yumsasmd
attempting to parse sasmd/shipped/vtxtan/100/vtxtan-100-x64_suse_linux_12-yumsasmd
attempting to parse sasmd/shipped/vtxtan/104/vtxtan-104-x64_redhat_linux_6-yumsasmd

as you can see the debug output contains no errors or warnings. The machine has access to the internet. I was also able to use the mirror manager to download all the rpm files in the order from the SAS repository into a local mirror repository. So connectivity should not be the issue.

Do you have other ideas what is going wrong?

Thank you for your help!

Re: SAS Viya 3.4 for Containers: error in deployment

SimonDawson — Tue, 09 Oct 2018 13:42:55 GMT

I'm getting the same output as you are.

$ docker run -it --rm -v 9c...3d:/tmp mirrormgr:3.4 list remote docker tags --deployment-data /tmp/SAS_Viya_deployment_data.zip --debug
evaulating path: licenses/SASViyaV0300_9C1458_Linux_x86-64.txt
evaulating path: licenses/SASViyaV0300_9C1458_70223818_Linux_x86-64.jwt
evaulating path: ca-certificates/SAS_CA_Certificate.pem
parsing ca cert
evaulating path: ca-certificates/SAS_CA_Certificate.p7b
evaulating path: entitlement-certificates/entitlement_certificate.pem
parsing client cert
evaulating path: entitlement-certificates/entitlement_certificate.pfx
evaulating path: order.oom
attempting to parse repos/shipped/connect/100/connect-100-x64_suse_linux_12-yum
attempting to parse repos/shipped/connect/104/connect-104-x64_redhat_linux_6-yum
...
attempting to parse sasmd/shipped/vtxtan/100/vtxtan-100-x64_suse_linux_12-yumsasmd
attempting to parse sasmd/shipped/vtxtan/104/vtxtan-104-x64_redhat_linux_6-yumsasmd
$

This is likely to do with the order being a few weeks older than it needs to be to be used in this way. If the order is reissued with the latest release I don't think you'll see this behavior. Please request a new order be generated with the latest software.

Re: SAS Viya 3.4 for Containers: error in deployment

AndreasMenrath — Tue, 09 Oct 2018 15:39:44 GMT

ok, i hope this will solve the issue.

Thank you for your support!

Re: SAS Viya 3.4 for Containers: error in deployment

AndreasMenrath — Thu, 11 Oct 2018 17:09:30 GMT

UPDATE: with the latest Software Order i can now see the Docker image and pull it from the SAS registry (which is btw extremely slow even in a cloud data center )