Yes. And also, possibly, no.

You push images to ECR. How you configure your image is up to you. Ideally, you&#39;d have an image with a single responsibility, but this is your decision. 

If you have multiple images, you push to multiple ECRs. If you have a single image doing many things, you can get away with a single ECR.

You can also push multiple images to the same ECR with creative use of tags (e.g. having the &quot;image name or flavour&quot; in the tag using your own naming convention.



1. It is recommended to push images with the version number of the same type. 

&gt; For example your-repo:1.1, your-repo:1.2

If you push images with the same that exist in the ECR repository than your old image will be replaced with the new image you are pushing.

 2. It depends on how your application is working. It is always advised to separate container working logically separate. 

&gt; For example The database image with a persistence volume. So, If a
&gt;     database container dies than it would not affect your data.

I downloaded the docker container for postgres: https://hub.docker.com/r/library/postgres/, and did the following:

    $ docker run --name satgres -e POSTGRES_PASSWORD=mysecretpassword -d -p 5432:5432 postgres
    satgres | &quot;docker-entrypoint.s…&quot; | 5 seconds ago | Up 6 seconds | 0.0.0.0:5432-&gt;5432/tcp | satgres
    $ docker exec -it c8f1b22cc41e /bin/bash        
    # psql -U postgres
    psql (10.1)
    postgres=# CREATE DATABASE mytest;
    postgres=# \password postgres
    postgres=# CREATE ROLE ming WITH LOGIN PASSWORD &#39;pass1234&#39;;
    postgres=# ALTER ROLE ming CREATEDB;
    postgres=# CREATE DATABASE sjk;
    postgres=# GRANT ALL PRIVILEGES ON DATABASE youtube TO ming;
    postgres=# \connect sjk
    youtube=# ALTER ROLE ming lOGIN;  

My plan is to use this database on docker with Django, so first want to check I can connect, but I cant.

    $ psql -h localhost -p 5432 -U postgres
    $ psql: FATAL:  role &quot;postgres&quot; does not exist
    $ psql -h localhost -p 5432 -U ming
    $ psql: FATAL:  role &quot;ming&quot; does not exist

I do the same with PSequal.app, says the same thing,
Im running on Mac High Sierra. 

Why am I getting this error? The role exists, or at least it seems it to me...

Postgresql Docker role does not exist

When I work on my personal C and C++ projects I usually put `file.h` and `file.cpp` in the same directory and then `file.cpp` can reference `file.h` with a `#include &quot;file.h&quot;` directive.

However, it is common to find out libraries and other kinds of projects (like the linux kernel and freeRTOS) where all `.h` files are placed inside an `include/` directory, while `.cpp` files remain in another directory. In those projects, `.h` files are also included with `#include &quot;file.h&quot;` instead of `#include &quot;include/file.h&quot;` as I was hoping.

I have some questions about all of this:

 1. What are the advantages of this file structure organization?
 2. Why are `.h` files inside `include/` included with `#include &quot;file.h&quot;` instead of `#include &quot;include/file.h&quot;`? I know the real trick is inside some Makefile, but is it really better to do that way instead of making clear (in code) that the file we want to include is actually in the `include/` directory?



Why create an include/ directory in C and C++ projects?

So I&#39;m new to ecs/ecr, but it seems like I have to name (with a tag) the image after the repository name in order to push that image to the repository.

So my question is: Is it intended that the user (me) would ONLY be pushing a single image and any associated versions of that image to a single repository in ecr, thus creating ANOTHER repository if i need to push a completely different image?

basically, one repo for nginx, one repo for postgressql, etc.

ECS/ECR: is common practice to have one repository per image (and associated versions)?

So I'm new to ecs/ecr, but it seems like I have to name (with a tag) the image after the repository name in order to push that image to the repository.
So my question is: Is it intended that the user (me) would ONLY be pushing a single image and any associated versions of that image to a single repository in ecr, thus creating ANOTHER repository if i need to push a completely different image?
basically, one repo for nginx, one repo for postgressql, etc.

From the console, I am invoking a lambda which submits a batch job. The batch job fails, indicating that ECS is unable to assume the role that is provided to execute the job definition.

For the role, I&#39;ve added the lambda and ECS services.

The error message:

&gt; &quot;ECS was unable to assume the role
&gt; &#39;arn:aws:iam::749340585813:role/golfnow-invoke-write-progress&#39; that
&gt; was provided for this task. Please verify that the role being passed
&gt; has the proper trust relationship and permissions and that your IAM
&gt; user has permissions to pass this role.&quot;

    &quot;TrainingJobRole&quot;: {
      &quot;Type&quot;: &quot;AWS::IAM::Role&quot;,
      &quot;Properties&quot;: {
        &quot;RoleName&quot;: &quot;golfnow-invoke-write-progress&quot;,
        &quot;AssumeRolePolicyDocument&quot;: {
          &quot;Version&quot;: &quot;2012-10-17&quot;,
          &quot;Statement&quot;: [
            {
              &quot;Effect&quot;: &quot;Allow&quot;,
              &quot;Principal&quot;: {
                &quot;Service&quot;: [
                  &quot;lambda.amazonaws.com&quot;,
                  &quot;ecs.amazonaws.com&quot;
                ]
              },
              &quot;Action&quot;: [
                &quot;sts:AssumeRole&quot;
              ]
            }
          ]
        },
        &quot;Path&quot;: &quot;/&quot;
      }
    }

The batch job:

        &quot;TrainingJob&quot;: {
      &quot;Type&quot;: &quot;AWS::Batch::JobDefinition&quot;,
      &quot;Properties&quot;: {
        &quot;Type&quot;: &quot;container&quot;,
        &quot;JobDefinitionName&quot;: {
          &quot;Fn::Sub&quot;: &quot;c12e-golfnow-${Environment}-job&quot;
        },
        &quot;ContainerProperties&quot;: {
          &quot;Image&quot;: {
            &quot;Fn::Join&quot;: [
              &quot;&quot;,
              [
                &quot;{{ image omitted }}&quot;,
                {
                  &quot;Ref&quot;: &quot;AWS::Region&quot;
                },
                &quot;.amazonaws.com/amazonlinux:latest&quot;
              ]
            ]
          },
          &quot;Vcpus&quot;: 2,
          &quot;Memory&quot;: 2000,
          &quot;Command&quot;: [
            &quot;while&quot;, &quot;True&quot;, &quot;;&quot;, &quot;do&quot;, &quot;echo&quot;, &quot;&#39;hello&#39;;&quot;, &quot;done&quot;
          ],
          &quot;JobRoleArn&quot;: {
            &quot;Fn::GetAtt&quot;: [
              &quot;TrainingJobRole&quot;,
              &quot;Arn&quot;
            ]
          }
        },
        &quot;RetryStrategy&quot;: {
          &quot;Attempts&quot;: 1
        }
      }
    },
    &quot;JobQueue&quot;: {
      &quot;Type&quot;: &quot;AWS::Batch::JobQueue&quot;,
      &quot;Properties&quot;: {
        &quot;Priority&quot;: 1,
        &quot;ComputeEnvironmentOrder&quot;: [
          {
            &quot;Order&quot;: 1,
            &quot;ComputeEnvironment&quot;: {
              &quot;Ref&quot;: &quot;ComputeEnvironment&quot;
            }
          }
        ]
      }
    }

Is the issue with the way it&#39;s being invoked? My user has admin privileges, so I don&#39;t think this is an issue with my user having insufficient permissions.

ECS unable to assume role

I&#39;m using AWS&#39;s CloudFormation, and I recently spent quite a bit of time trying to figure out why the role I had created and attached policies to was not enabling my ECS task to send a message to a Simple Queue Service (SQS) queue. 

I realized that I was incorrectly attaching the SQS permissions policy to the `Execution Role` when I should have been attaching the policy to the `Task Role`. I cannot find good documentation that explains the difference between the two roles. CloudFormation documentation for the two of them are here: [ExecutionRole](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-ecs-taskdefinition.html#cfn-ecs-taskdefinition-executionrolearn) and [TaskRole](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-ecs-taskdefinition.html#cfn-ecs-taskdefinition-taskrolearn)

Difference between AWS Elastic Container Service&#39;s (ECS) ExecutionRole and TaskRole

I am trying to understand what is difference between AWS Athena service and the newly released S3 select (still in preview).

How are use cases different for both of those? It seems both help in selecting partial data from S3.

What is difference between AWS S3 Select and AWS Athena?

I have successfully launched new AWS RDS PostgreSQL *v10* instance and need to install PostgreSQL v10 client on Amazon Linux EC2 instance.

I have tried to install it with `yum`, but it cant find the package for v10:

    [ec2-user@ip-X-X-X-X ~]$ sudo yum install -y postgresql10
    Loaded plugins: priorities, update-motd, upgrade-helper
    amzn-main      | 2.1 kB  00:00:00
    amzn-updates  | 2.5 kB  00:00:00
    No package postgresql110 available.
    Error: Nothing to do

Previously I managed to install PostgreSQL client v9.5 with:

    [ec2-user@ip-X-X-X-X ~]$ sudo yum install -y postgresql95

I guess I need to add Postgres yum repository, as mentioned in https://www.postgresql.org/download/linux/redhat/. But what Platform should I choose for Amazon Linux? Red Hat?

Installing PostgreSQL Client v10 on AWS Amazon Linux (EC2) AMI

Updated answer (7/10/2021): For AWS CLI v1, do this:

```bash
export AWS_DEFAULT_PROFILE=user2
```

For AWS CLI v2, the following will work:

```bash
export AWS_PROFILE=user2
```

The full question is below for context:

----------

(1.) After successfully configuring a second profile for the AWS CLI, I unsuccessfully tried to set the profile to user2 in my bash session with the following command:

    export AWS_PROFILE=user2

... per the advice here: https://docs.aws.amazon.com/cli/latest/userguide/cli-multiple-profiles.html

(2.) The following command works: 

```bash
aws s3 ls --profile user2
```

So I know that the AWS CLI and the user2 profile are both working on my computer.

(3.) However, when I subsequently (that is, after entering &quot;export AWS_PROFILE=user2&quot;) try something like:

```bash
aws s3 ls
```

... AWS&#39;s response assumes that I want to query it as the default user (NOT user2)

(4.) So the only way I can use the user2 profile from the command line is by continuing to append &quot;--profile user2&quot; to every single command, which is tedious.


(5.)

```bash
echo $AWS_PROFILE
```

yields:

```bash
&gt;&gt; user2
```

, as expected.


Any idea what&#39;s going on here? I&#39;m sure I&#39;m making some dumb mistake somewhere.

How to temporarily switch profiles for AWS CLI?

When I try to run simple docker commands like:

    $ docker ps -a

I get an error message:

&gt; Got permission denied ... /var/run/docker.sock: connect: permission denied

When I check permissions with

    $ ls -al /var/run/

I see this line:

    srw-rw---- root docker docker.sock

So, I follow an advice from many forums and add local user to docker group:

    $ sudo usermod -aG docker $USER

But it does not help. I still get the very same error message. How can I fix it?

docker.sock permission denied

After I run this  
 `$ docker run --rm -v &quot;/c/users/vipul rao/documents/github/wappalyzer:/opt/wappalyzer&quot; -it wappalyzer/dev`

 I am getting the following error 

&gt; the input device is not a TTY.  If you are using mintty, try prefixing the command with &#39;winpty&#39;

What should I use here? I am running Docker on Windows 8 in MINGW64.

docker error : the input device is not a TTY. If you are using mintty, try prefixing the command with &#39;winpty&#39;

My docker containers are running in a local network, called my_local_network. To assure the network exists, every build script starts with:

    docker network create --driver bridge my_local_network

This works fine. If the network does not exist, it is created, if not, nothing happens. Except for the error message:

    Error response from daemon: network with name my_local_network already exists

Is there a way to tell docker only to create the network if it doesn&#39;t exist?



Docker create network should ignore existing network

**TL;DR:** Why does an aspnet core app run on port 80 from within a Docker image, but 5000 outside a docker image. 


**Elaborate**

I went through the aspnet core / docker tutorial found here:
https://docs.microsoft.com/en-us/dotnet/core/docker/building-net-docker-images

Half way through the page, I start the application with the following as prescribed: 

    dotnet run

Among other things, this prints this:

    Now Listening on: http://localhost:5000

Great. That is what I expected. The next thing in the tutorial is to start the exact same application from within a Docker image. 

    docker build -t aspnetapp .
    docker run -it --rm -p 5000:80 --name aspnetcore_sample aspnetapp

This results in 

    Now listening on: http://[::]:80

Wait. Wat? **Why is the aspnet core app running on port 80?** It was running on port 5000 when I ran it directly from the machine. There were no configuration file changes. 

I suspect that it has something to do with the base docker images, but am not yet skilled enough in docker to track this down. 

Why does aspnet core start on port 80 from within Docker?

How can I create an AWS ECR repository if it doesn&#39;t already exist?

Create AWS ECR repository if it doesn&#39;t exist

When I deploy using cloudformation ```aws cloudformation deploy --region $region --stack-name ABC```

Got error: 

&gt; An error occurred (ValidationError) when calling the CreateChangeSet
&gt; operation:
&gt; Stack:arn:aws:cloudformation:stack/service/7e1d8c70-d60f-11e9-9728-0a4501e4ce4c
&gt; is in ROLLBACK_COMPLETE state and can not be updated.

Please help me !

ValidationError Stack:arn aws cloudformation stack is in ROLLBACK_COMPLETE state and can not be updated

I am trying to run a private repository on aws-ecs-fargate-1.4.0 platform.

For private repository authentication, I have followed the [docs][1] and it was working well.

Somehow after updating existing service many times it goes fail to run the task and complain the error like 

    ResourceInitializationError: unable to pull secrets or registry auth: execution resource retrieval failed: unable to get registry auth from asm: service call has been retried 1 time(s): asm fetching secret from the service for &lt;secretname&gt;: RequestError: ...

I haven&#39;t change the `ecsTaskExecutionRole` and it contains all required policies to fetch secret value.

 1. AmazonECSTaskExecutionRolePolicy
 2. CloudWatchFullAccess
 3. AmazonECSTaskExecutionRolePolicy
 4. GetSecretValue
 5. GetSSMParamters



  [1]: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/private-auth.html

Aws ecs fargate ResourceInitializationError: unable to pull secrets or registry auth

I am trying to deploy a docker configuration with images on a private docker registry.

Now, every time I execute `docker login registry.example.com`, I get the following error message:

&gt; error getting credentials - err: exit status 1, out: `Cannot autolaunch D-Bus without X11 $DISPLAY`

The only solution I found for non-MacOS users was to run `export $(dbus-launch)` first, but that did not change anything.

I am running Ubuntu Server and tried with both the Ubuntu Docker package and the Docker-CE package.

How can I log in without an X11 session?

docker login fails on a server with no X11 installed

I am trying to set up docker image of amazon ECR on ```ubuntu18.04``` machine of AWS,using commands provided by ```view push commands``` of ```Amazon Container Services```
[![view push commands of amazon container services][1]][1]

 ,please note i have already set up ```docker``` on my ```ubuntu18.04``` and also output of ```docker -v``` is as below

    ubuntu@ip-172-31-0-143:~$ docker -v
    Docker version 19.03.7, build 7141c199a2


  [1]: https://i.stack.imgur.com/x8w8O.png

When i execute the command provided by amazon container services on aws cli on ubuntu18.04 i get error as
    Error: Cannot perform an interactive login from a non TTY device

The command which i am using is 

    aws ecr get-login-password --region us-west-2 | docker login --username AWS --password-stdin 8233251134332.dkr.ecr.us-east-2.amazonaws.com/gatling-lots

please note i have successfully configured awscli and i can see the
detailed  from ```aws s3 ls```

Here is detailed error log
 
    ubuntu@ip-172-31-0-143:~$ aws ecr get-login-password --region us-   
    east-2 | docker login --username AWS --password-stdin 
    823443336.dkr.ecr.us-west-2.amazonaws.com/gatling-lots
    usage: aws [options] &lt;command&gt; &lt;subcommand&gt; [&lt;subcommand&gt; ...]      
    [parameters]
     To see help text, you can run:

    aws help
    aws &lt;command&gt; help
    aws &lt;command&gt; &lt;subcommand&gt; help
    aws: error: argument operation: Invalid choice, valid choices are:

     batch-check-layer-availability           | batch-delete-image                      
     batch-get-image                          | complete-layer-upload                   
    create-repository                        | delete-lifecycle-policy                 
    delete-repository                        | delete-repository-policy                
     describe-images                          | describe-repositories                   
     get-authorization-token                  | get-download-url-for-layer              
     get-lifecycle-policy                     | get-lifecycle-policy-preview            
     get-repository-policy                    | initiate-layer-upload                   
     list-images                              | put-image                               
     put-lifecycle-policy                     | set-repository-policy                   
     start-lifecycle-policy-preview           | upload-layer-part                       
     get-login                                | help                                    
     Error: Cannot perform an interactive login from a non TTY device

output of

    ubuntu@ip-172-31-0-143:~$ (aws ecr get-login --no-include-email  --region us-east-2)

    docker login -u AWS -p 
    
    MzQxL2c0Yks4RjVxeDg9IiwidmVyc2lvbiI6IjIiLCJ0eXBlIjoiREFUQV9LRVkiLCJleHBpcmF0aW9uIjoxNTgzNjgzNDY5fQ== https://825251119036.dkr.ecr.us- east-2.amazonaws.com

Content Type	Original Author	Original Content on Stackoverflow
Question	aphexlog	View Question on Stackoverflow
Solution 1 - Amazon Web-Services	MrDuk	View Answer on Stackoverflow
Solution 2 - Amazon Web-Services	mohit	View Answer on Stackoverflow

ECS/ECR: is common practice to have one repository per image (and associated versions)?

Amazon Web-Services Problem Overview

Amazon Web-Services Solutions

Solution 1 - Amazon Web-Services

Solution 2 - Amazon Web-Services

Why create an include/ directory in C and C++ projects?

Postgresql Docker role does not exist

Attributions