Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug: Unable to pull docker image on some ssh targets #5481

Closed
zentron opened this issue Apr 14, 2019 · 3 comments

Comments

@zentron
Copy link

commented Apr 14, 2019

A bug appears to have been introduced for some platforms when the Docker Acquisition step runs.

An example of the messages that appear in the logs

Feed type provided Docker using DockerImagePackageDownloader
bash: Calamari/Temp/5f251161-9c57-4807-9220-aacde2746244/Bootstrap.d41-4bd3-b222-d6a6c4343caa.Octopus.DockerPull.sh: No such file or directory
Failed to download package mongo v4.1.10 from feed: 'https://index.docker.io'
Unable to pull Docker image

Is appears as though the script is having some problems writing to the temp directory on some ssh targets.

@zentron zentron self-assigned this Apr 14, 2019
@zentron zentron closed this Apr 15, 2019
@zentron

This comment has been minimized.

Copy link
Author

commented Apr 15, 2019

New version of Calamari in 2019.4.3 writes temporary files into current working directory rather than filesystem temp location. Preliminary test with one customer's instance indicates this resolves the problem.

@zentron zentron added this to the 2019.4.3 milestone Apr 15, 2019
@joelhays

This comment has been minimized.

Copy link

commented Apr 19, 2019

@zentron any thoughts on how to fix this on 2019.3.0 LTS when upgrading is not an option?

@lock

This comment has been minimized.

Copy link

commented Jul 18, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. If you think you've found a related issue, please contact our support team so we can triage your issue, and make sure it's handled appropriately.

@lock lock bot locked as resolved and limited conversation to collaborators Jul 18, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
2 participants
You can’t perform that action at this time.