Public Repository

Last pushed: 16 days ago
Short Description
Amazon Linux 2017.03 (minimal 60mb)
Full Description

I posted how to create an Amazon Linux image on the AWS Developer Forum ( copied from ) :

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).

  1. Boot up an amazon linux ami (I used amzn-ami-hvm-2016.03.0.x86_64-gp2).
  2. yum install -y docker && service docker start
  3. wget -q
  4. bash 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.

Docker Pull Command

Comments (9)
16 days ago

Updated Amazon Linux 2017.03 (Please note that the image/os name remains 2017.03). Package diffs:


4 months ago

Updated Amazon Linux 2017.03

a year ago

I'll just leave this here. If you have troubles with https sites, install the ca-certificates package.

a year ago

Updated Amazon Linux 2016.03 with latest fixes/patches

a year ago

2 years ago

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'
2 years ago

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: [8] System error: exec: "/bin/bash": stat /bin/bash: no such file or directory

Did you face similar issues while running the script?

2 years ago

@pradtke, yes you have to build it on an EC2 host. The Amazon Linux yum repos are only accessible within EC2.

2 years ago

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.