nateleiby
The main downsides I see are:
(1) It would affect people's Docker workflow
docker pull org/foo:tag
->
aws ecr get-login
<run docker login command>
docker pull some-aws-url/foo:tag
(2) We need to keep some history (to allow rolling back apps). So either need that in DockerHub or would need to move old images to ECR if we planned to fully nuke our DockerHub account.
Ask HN: What AWS Region does DockerHub run in?
We are looking to run two Docker registries, so that we're resilient to a DockerHub outage, like the one that happened during the great AWS S3 outage at the end of Feb.One option would be to push our images to AWS ECR in addition to DockerHub, but we'd want to be sure that ECR is running a different region than DockerHub.Thanks!
Ask HN: What is your docker registry setup?
I'd like to ensure that our build and deploy process is reliable and speedy when pushing/pulling Docker images.Using DockerHub, I have seen some reliability issues (downtime, sometimes without status page updates), bugs (timeout querying DockerHub API when a repo has many tags), and behavior changes (images used to be immediately available after push, now it appears to be async).Given the...
Aviator: locally launch a service and all its dependent services
(1) specifically state that `pip freeze` is how to create requirements file (as folks have said in comments already) (2) add "further reading" link on VirtualEnvWrapper, as it adds some convenience methods to ease use of VirtualEnv (3) the "yolk" package shows you what's currently installed; it can be helpful to `pip install yolk` then run `yolk -l` to view the different packages installed in each of your envs. (4) when installing a package, you can specify the version, e.g. `pip install mod==1.1`, whereas `pip install mod` will simply install the latest