Skip to content

Latest commit

 

History

History
51 lines (46 loc) · 2.24 KB

troubleshooting.md

File metadata and controls

51 lines (46 loc) · 2.24 KB
Raw

Troubleshooting

You may want to first try:

  • Rerunning your aladdin command with --init flag
  • Restarting your LOCAL cluster via k3d cluster delete LOCAL && aladdin --init and then rerunning your command

Specific Issues

InvalidSignatureException

Fix this by restarting your LOCAL cluster via k3d cluster delete LOCAL && aladdin --init and then rerunning your command

Problems with git processing during aladdin deploy or publish

If your error is something like this:

Cloning into '/tmp/tmp7sihubxt'...
Bad owner or permissions on /root/.ssh/config
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

try: chmod 6000 ~/.ssh/config before rerunning your command

Alternative solution: ssh-agent

If the above does not resolve the issue or causes other issues, you may wish to consider running an ssh-agent and adding your private keys to that. You can then make the agent available to the aladdin container rather than mounting your ~/.ssh directory into it.

Once you have the agent running and added your private keys, instruct aladdin to set the SSH_AUTH_SOCK environment variable and mount the SSH_AUTH_SOCK file as a volume by setting the ssh.agent aladdin config value to true. This will disable the mounting of the ~/.ssh directory, as well.

aladdin config set ssh.agent true

Error: could not find tiller

Rerun your aladdin command with --init flag to initialize tiller via helm

Error: could not find a ready tiller pod

Tiller is still initializing. Wait a minute, and then rerun your aladdin command.

Aws parsing issues

Make sure your ~/.aws/credentials file is of this format:

[{profile-name-1}]
aws_access_key_id =  {your profile-name-1 access key id}
aws_secret_access_key =  {your profile-name-1 secret access key}
[{profile-name-2}]
aws_access_key_id =  {your profile-name-2 access key id}
aws_secret_access_key =  {your profile-name-2 secret access key}

and make sure your ~/.aws/config file is of this format:

[profile {profile-name-1}]
output = json
region = {your profile-name-1 aws region}
[profile {profile-name-2}]
output = json
region = {your profile-name-2 aws region}