This repository was archived by the owner on Apr 27, 2021. It is now read-only.
#3 Update package list before imagemagick install #6
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I was having the same problem as @drewbryant when running through the python compute demo. Connecting to my compute vm with SSH and manually running 'sudo apt-get install imagemagick' I was seeing 'E: Package 'imagemagick' has no installation candidate'. So I tried updating apt's package index using 'sudo apt-get update' and everything worked.
Finally, I went back and tried adding the package update to startup.sh and ran the whole demo again. This time the final image showed up correctly at the expected gcs bucket url.