[A2C] [BUG]: containerize fails because it uses amazonlinux:32 docker image

### Community Note

* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request
* Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
* If you are interested in working on this issue or have submitted a pull request, please leave a comment

**Tell us about your request**
Container using A2C app2container fails due to wrong docker image

**Which service(s) is this request for?**
A2C app2container

**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
Executing app2container gives an error
```ERROR ~[containerize java-jboss-8cfbfd48] 2020/07/28 18:40:59 Error running docker build, out: Sending build context to Docker daemon 2.826GB
Step 1/97 : FROM amazonlinux:32
manifest for amazonlinux:32 not found: manifest unknown: manifest unknown
, err: exit status 1
ERROR ~[containerize java-jboss-8cfbfd48] 2020/07/28 18:40:59 Internal error occurred
⚠️ Error building docker image```

Because it effectively has a `FROM amazonlinux:32`in the Dockerfile, and it can not find the image in Dockerhub

**Are you currently working around this issue?**
I'm stuck as documentation doesn't provide any solution

**Additional context**

**Attachments**

Start by reproducing the App2Container containerize failure for the java-jboss example and inspect the generated Dockerfile entry using FROM amazonlinux:32. Confirm which available base image should replace it, then verify that the Docker build completes without the manifest error.

Written by the indexing model from the issue text.