I posted how to create an Amazon Linux image on the AWS Developer Forum ( copied from https://forums.aws.amazon.com/message.jspa?messageID=574500 ) :
For anyone interested, I got this working. I'd push up the image to the registry, but I'm not sure if I have permission to do so. If someone from AWS would like, I can put the file somewhere (~100mb).
- Boot up an amazon linux ami (I used amzn-ami-hvm-2016.03.0.x86_64-gp2).
- yum install -y docker && service docker start
- wget -q https://raw.githubusercontent.com/docker/docker/master/contrib/mkimage-yum.sh
- bash mkimage-yum.sh ambakshi/amazon-linux
At this point you have an image with the specified name, tagged by the os version. You can run it, retag it and push it to a private registry, export it, etc. Came in real handy during our move from centos to amazon linux when I was testing puppet.
Updated Amazon Linux 2017.03 (Please note that the image/os name remains 2017.03). Package diffs:
Updated Amazon Linux 2017.03
I'll just leave this here. If you have troubles with https sites, install the ca-certificates package.
Updated Amazon Linux 2016.03 with latest fixes/patches
Updated to the latest Amazon Linux GA build. It's still called 2015.09.
@sameer2086: Try the latest one, it's working for me.
$ docker run -i -t --rm ambakshi/amazon-linux:2015.09 bash -c 'echo success' success
I tried creating the image but it's failing with following error
- docker run -i -t --rm amazon-linux:amazon-linux /bin/bash -c 'echo success'
exec: "/bin/bash": stat /bin/bash: no such file or directory
Error response from daemon: Cannot start container 4d5a2efe973a4d3dc68eb6f82a820a348d04b8798d731e6ca902c889001cf637:  System error: exec: "/bin/bash": stat /bin/bash: no such file or directory
Did you face similar issues while running the script?
@pradtke, yes you have to build it on an EC2 host. The Amazon Linux yum repos are only accessible within EC2.
How did you get it to work with Amazon's RPM repos? Did you build your docker images from an EC2 host? If I try building an image on my latop, from this one then I get 403s talking to the rpm repos.