Solving problem with «The container name ... is already in use by container»
How to deal with container naming issue during update of container version
How to deal with container naming issue during update of container version
Let’s make it all work: private AWS ECR repository + custom external domain + ECR Credentials Helper Login + control permissions to fetch your images via Cognito
How to be able to use your custom domain when accessing docker repository hosted in private AWS ECR.
How to easily revert to previously deployed docker image in case new version of your app behaves abnormally?
Root cause of a weird ’linux/arm/v7 not supported error'.
Some time ago I started to play with AngularJS to create a simple side-project app. During this work I realized that I don’t like the differences between how the application works depending on the environment where I deploy it (localhost - faster and Docker on VPS - slower). The UX was quite poor for slower network connection and I decided to do something about that. The user experience was increased by applying some simple rules like:...
JBoss Keycloak is available as a Docker image. It’s all fun and games until you’ll try to run it behind SSL reverse proxy like I do for all my services. Despite settings all required HTTP headers on the proxy side (Nginx in my case) like: proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-Proto $scheme; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; it fails to pass all the requests to the Docker Keycloak image (running on Wildfly server)....