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.

Sign up for GitHub

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

Jump to bottom

StarCluster AMIs are incompatible with t1.micro #52

Closed
npinto opened this issue Oct 3, 2011 · 3 comments
Closed

StarCluster AMIs are incompatible with t1.micro #52

npinto opened this issue Oct 3, 2011 · 3 comments
Labels
Release

Comments

@npinto
Copy link

npinto commented Oct 3, 2011

There seems to be an issue when trying t1.micro with StarCluster AMIs, e.g.:

% ec2-run-instances -key kp ami-bf5eb9d6 -t t1.micro
Client.UnsupportedOperation: AMI 'ami-bf5eb9d6' with an instance-store
root device is not supported for the instance type 't1.micro'.

FYI, the same error was experienced in CS264 (but no answer was given the student):
http://forum.cs264.org/index.php?topic=411.0
@jtriley
Copy link
Owner

jtriley commented Oct 7, 2011

An EBS-backed AMI must be used with the t1.micro instance type. I'll push out public EBS AMIs in us-east zone soon...

@npinto
Copy link
Author

npinto commented Oct 10, 2011

Awesome! Thanks @jtriley!

@jtriley
Copy link
Owner

jtriley commented Jan 4, 2012

Done, latest AMIs are out. Use 'starcluster listpublic' in any AWS region to find the new EBS-backed Ubuntu 11.10-based StarCluster AMIs (including new HVM w/ GPU tools)

@jtriley jtriley closed this as completed Jan 4, 2012
vasisht pushed a commit to vasisht/StarCluster that referenced this issue Jul 19, 2016
Merge pull request jtriley#52 from vasisht/datacratic_vanilla_improve…
49c10db 
…ments

* Update to EFS plugin
* setup boto3 check
* template SUBNET_IDS
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Release
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@npinto @jtriley