41 lines (31 loc) · 1.83 KB

Docker registries, repositories, images & tag hierarchy source:
- A Docker registry is a service that is used to store docker repositories (e.g. DockerHub, AWS ECR).
- A Docker repository is a collection of related images (usually of the same name with different tags).
- A tag is a unique alphanumeric identifier associated with a specific version.
- This is why in setup_aws_resources.sh, the correct command is:
```
 # $repo_url variable = 595614743545.dkr.ecr.us-east-1.amazonaws.com/ml-server
 $ docker tag ml-server $repo_url
 $ docker push $repo_url:latest
```
instead of:
```
 $ docker tag ml-server $repo_url/ml-server 
 $ docker push $repo_url/ml-server:latest
```
- 595614743545.dkr.ecr.us-east-1.amazonaws.com/ml-server
  - italic = registry
  - bold = repository
  - The variable $repo_url contains both the registry and the repository.

Things to research

execution role ARN vs task role ARN

IGW

Error: (ResourceInitializationError: unable to pull secrets or registry auth: pull command failed: : signal: killed)
- Solution: you need to make sure there is an IGW that is attached to your VPC and the subnet in which you service is running!!!
- See here
You don't have to manually specify traffic forwarding from an instance/ALB to an IGW; the fact that the IGW exists ensures that traffic that is destined for the internet will go through the ALB.

General Notes

2021-08-11: Went back to the master branch and am getting the same ResourceInitializationError as above. I doubt I would have pushed from remote to origin with this happening.