packer-ecs | Packer ECS Image | AWS library

by jmenga Shell Version: Current License: No License

X-Ray Key Features Code Snippets Community Discussions(1)Vulnerabilities Install Support

kandi X-RAY | packer-ecs Summary

packer-ecs is a Shell library typically used in Cloud, AWS applications. packer-ecs has no bugs, it has no vulnerabilities and it has low support. You can download it from GitHub.

Packer ECS Image

Support

Quality

Security

License

Reuse

Support

packer-ecs has a low active ecosystem.

It has 11 star(s) with 6 fork(s). There are 2 watchers for this library.

It had no major release in the last 6 months.

packer-ecs has no issues reported. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of packer-ecs is current.

Quality

packer-ecs has no bugs reported.

Security

packer-ecs has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

License

packer-ecs does not have a standard license declared.

Check the repository for any license declaration and review the terms closely.

Without a license, all rights are reserved, and you cannot use the library in your applications.

Reuse

packer-ecs releases are not available. You will need to build from source code and install.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of packer-ecs

Get all kandi verified functions for this library.

packer-ecs Key Features

No Key Features are available at this moment for packer-ecs.

packer-ecs Examples and Code Snippets

No Code Snippets are available at this moment for packer-ecs.

Community Discussions

Trending Discussions on packer-ecs

AWS Using ECS-Optimized AMI with Docker Containers in ECS

QUESTION

AWS Using ECS-Optimized AMI with Docker Containers in ECS

Asked 2019-May-03 at 20:46

I have used an extensive amount of time building the kind of deployment setup I'm going to describe next. I've gone through most of the documentation on ECS and documented an exhaustive list of learning resources.

However, it seems I'm still missing some vital piece of this puzzle with Docker on AWS ECS...

In development, we are using Docker Compose for defining a set of containers as a local full-stack cluster. It is a really convenient tool for working with containers locally.

Our aim is to use Docker Compose approach for deploying this cluster into Amazon AWS ECS.

ECS supports Compose file format up to version 3.0. Most notably there is no support for using local files as the build context, so an image must be referenced.

What I'm currently confused with:

The official doc states that instances running in ECS should have Amazon ECS container agent, Docker daemon, and ecs-init installed and configured. As such, for the base image they are recommending:

The Amazon ECS-optimized AMIs are preconfigured with these requirements and recommendations. We recommend that you use the Amazon ECS-optimized Amazon Linux 2 AMI for your container instances unless your application requires a specific operating system or a Docker version that is not yet available in that AMI.

Confusion point 1: However, I've found no examples in the official docs on how to actually build and run Docker containers based on these optimized AMIs... There are just about two Dockerfile examples, here and here, which are both building from public non-AMI images?

I've found some resources, like here (source) and here, which show how to use Packer with its EC2 AMI Builder (EBS backed) for building a custom AMI based on these ECS optimized AMIs.

I've set up this process myself with some minor modifications, and it is working. I have my own custom images showing up under AWS EC2 AMIs.

Confusion point 2: However, I seem unable to reference these AMI images in my dockerfiles or docker compose files, as they are not stored in ECR... Am I correct (or having misconfig)?

Packer does have a post-processor for docker push which has support for ECR. But it does not work with EC2 AMI Builder:

...

ANSWER

Answered 2019-May-03 at 20:46

There's a split between the software running on the host itself and the software running in containers. The paragraph you're reading is about software that needs to run on the host EC2 systems.

When you set up an ECS cluster, you need to provide a set of EC2 instances. AWS recommends you use their AMI as a base for those instances, and this is a pretty reasonable thing to do. If you want to use something like the standard Ubuntu AMI instead, you need to install the referenced bits of software on those instances before it can "be part of" the ECS cluster and start running containers. (To run Docker containers you need Docker installed on the host.)

I don't think there are particular requirements on the containers that run on ECS, and there isn't a way to build a Docker image based on an AMI. You should be able to launch the same set of images you're using locally (assuming you actually COPY the source code into the images, they run without operator interaction, etc.).

Source https://stackoverflow.com/questions/55976745

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install packer-ecs

You can download it from GitHub.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: