search

ibm-cloud-architecture / terraform-icp-ibmcloud

This Terraform example configurations uses the IBM Cloud provider to provision virtual machines on IBM Cloud Infrastructure (SoftLayer) and TerraForm Module ICP Deploy to prepare VSIs and deploy IBM Cloud Private on them in Highly Available configuration. This Terraform template automates best practices learned from installing ICP on IBM Cloud Infrastructure.
12 stars 21 forks source link

ICP 2.1.0.3: Docker login fails #5

Open jesusmah opened 5 years ago

jesusmah commented 5 years ago

I am using @hassenius refactor branch (which I assumed should contain the latest and the greatest) to install ICP 2.1.0.3 on IBM Cloud. However, it fails during docker login at the icp-install terraform step:

module.icpprovision.null_resource.icp-install (remote-exec): fatal: [10.144.149.222]: FAILED! => {"changed": true, "cmd": "echo '820b575a1dd326c0d197146cfc3c58f1' | docker login -u icpdeploy --password-stdin placeholder.com || docker login -u icpdeploy -p 820b575a1dd326c0d197146cfc3c58f1 placeholder.com", "delta": "0:00:12.383889", "end": "2018-10-10 23:29:14.400387", "msg": "non-zero return code", "rc": 1, "start": "2018-10-10 23:29:02.016498", "stderr": "Error response from daemon: login attempt to https://placeholder.com/v2/ failed with status: 404 Not Found\nWARNING! Using --password via the CLI is insecure. Use --password-stdin.\nError response from daemon: login attempt to https://placeholder.com/v2/ failed with status: 404 Not Found", "stderr_lines": ["Error response from daemon: login attempt to https://placeholder.com/v2/ failed with status: 404 Not Found", "WARNING! Using --password via the CLI is insecure. Use --password-stdin.", "Error response from daemon: login attempt to https://placeholder.com/v2/ failed with status: 404 Not Found"], "stdout": "", "stdout_lines": []}