docker-remote-api | Docker Remote API model for Java | REST library

I have the following set up:

• AWS Elastic Container Registry
• Elastic Container Service
• Application Load Balancer
• Cluster,
• Service
• Task

I have been getting a 503 service temporarily unavailable from my API. I have determined this means that I don't have any instances in my target group.

When I add the instance created by the cluster, service, task to the target group it joins for a few minutes then starts draining without me doing anything. Earlier it was staying but was determined to be unhealthy and I was getting a 502 bad gateway when it was like that. It seems to me that it needs to be healthy in order for it to stay? Is there something that I'm missing?

Service Task Json Definition

I want to run a simple LAMP application on ECS Fargate.

I can't access the Mariadb container from the PHP (Laravel) container.

(Same error with php artisan migrate on ECS Exec)

In this article, it seems to be possible to communicate with localhost in the same task, but I am having trouble accessing it.

Linking Container in AWS Fargate error

SQLSTATE[HY000] [2002] No such file or directory (SQL: ...

Both Laravel and MariaDB containers are managed by ECR with a built Dockerfile.

*Currently, there are a lot of things to tweak, but I'm aiming to get it working first, so some of them are superfluous.

I am defining a task in AWS which I already have working using aws_ecs_task_definition module. I am setting up some environtment variables using the environtment var in terraform module but some of the will be provided throug AWS SSM. The normal creation without AWS SSM is:

I am trying to Deploy my image present in ECR using AWS ECS Fargate via Github Actions. It is a Github private repository as well as a private ECR repository. The AWS secrets are properly configured. I have also created an ecsTaskExecutionRole and included it in the Task Definition as per the AWS docs here. But the following error persists:

We have a docker images being stored in ECR, some have come from a TC build agent and some have come from builds on local developer machines. All images can be pulled an run locally but when trying to start the images built on the build TC build agents we get the following error when the ECS cluster starts running the task.

InternalError: failed to normalize image reference "http://xxx.eu-west-1.amazonaws.com/events/name-of-contianer:tag"

I can't seem to find any additional info in the logs, or mention of an error for normalize in any of the ECS docs. Has anyone experienced this error, or even know what it means!

ECS Task Definition:

I want to connect to Docker TCP socket running in WSL2 via PyCharm. I can't seem to expose the socket, I think possibly because there's limited control of docker-daemon within WSL2 (systemctl)? I can't use Docker Desktop because I need GPU support (Windows Dev Channel + nvidia-docker). I've tried the following:

I would like to access the Docker API (running on Windows Server). Sadly a TCP connection is not possible in our network (at least for this case).

Here I found a solution to change the port. But I am not sure if changing the protocol is possible?

How to apply a specific plugin version using newer Gradle syntax? I would like to do something like this but this gives an error of unknown property 'version':