Top link points to a non-existent AMI so this "recipe" -- like almost every "here's how to ..." recipe on GitHub that gets posted on HN -- doesn't work. I swear, it's like 100% fail on these types of posts.
Also this "real GPU" is explicitly called out in the Google docs as unsupported.
I can't ssh into instance using the AWS documentation (I was pretty careful following the instructions and know I have the right instance id and region)--> "Permission denied (publickey)."
(I've since fixed this - I hadn't chmod'd right, and didn't account for working from an ubuntu machine)
Comments
Top link points to a non-existent AMI so this "recipe" -- like almost every "here's how to ..." recipe on GitHub that gets posted on HN -- doesn't work. I swear, it's like 100% fail on these types of posts.
Also this "real GPU" is explicitly called out in the Google docs as unsupported.
I can't ssh into instance using the AWS documentation (I was pretty careful following the instructions and know I have the right instance id and region)--> "Permission denied (publickey)."
(I've since fixed this - I hadn't chmod'd right, and didn't account for working from an ubuntu machine)
I tried with the Oregon region and it failed. I changed to the N. California region and it worked. (No comment about the GPU though.)
Github recipes are the "works on my machine!" of the new millennium. Just like pecking in programs from computer magazines in the 1980s, only better!
I like the ones that are hardcoded to a specific name in a home directory best. Especially when it doesn't match the github name of the "creator."
I've added a note that the AMI's region must be us-west-1. Thanks for the heads up!
An AMI id is region-specific, the original poster should probably have mentioned what region he created the AMI in.