dind | recipe lets you run Docker within Docker | Continuous Deployment library

I'm in a Spring course, and I have a maven application (downloaded from the course resources) built from spring initializr. I can build a local Docker image with mvn spring-boot:build-image (no Dockerfile in the project). By default a Docker image is built as linux/amd64, but I am working with a M1 Apple Silicon chip (arm64). I've been looking many workarounds but with no success. Lastly, I found that maybe adding a Dockerfile and specifying the platform it would build the image accordingly.

My goal is to build a docker image for arm64 architecture.

So, I created a Dockerfile:

I'm receiving the below error message in my GitLab pipeline when attempting to create a docker image and then push it up to my docker hub account. It seems to be a syntax issue and I have tried a few combinations but cannot get it to work.

Can anybody help? Thanks.

I setup a GitLab runner on EC2 which triggers jobs on a Fargate ECS cluster. I followed this tutorial step by step: https://docs.gitlab.com/runner/configuration/runner_autoscale_aws_fargate

During my CI/CD I build docker image then I want to reuse them during other stages of my CI/CD. So when I used shared runner I used docker dind:

I am a newbie in gitlabci. I want to understand why do we need docker dind image in order to build a docker image in GitLab CI jobs. Why can't we use the docker executor and run docker commands under scripts?

When we register docker executor gitlab runner, we choose one image.. Again inside gitlabci, we choose an image under image: or services: fields. So does that mean this GitLab CI job container runs inside the docker executor container?

I'm using aws runner for running my CI job Below is my CI code

I am trying to simulate a development environment in a Docker container. As part of this effort, I want the Docker container to have the same users and groups as the host. This can be achieved by mounting the host's user and group configuration file when running docker run (see the full docker run command at the bottom).

When you start this container, you login into the container as the same user and group as on the host (specifying the flag --user $(id -u):$(id -g)). Suppose that user is ubuntu and that group is also ubuntu.

Now, I also want to be able to run Docker commands from within the container. I attempt doing this by mounting the docker socket file so the Docker client in the Docker container can communicate with the Docker daemon on the host.

On the host, the login user has been added to the group docker and the docker socket file permissions are set such that any user in the group docker can issue docker commands:

I have a spring-boot application with mysql database connection and junit test classes. That's working fine in local machine. But when I pushed the code to Gitlab to build a CI/CD pipeline, the build stage is failing due to mysql connection issue.

application.yml

This is my first time trying to CI to Google Cloud from Gitlab, so far has been this journey very painful, but I think I'm closer.

I follow some instructions from:

https://medium.com/google-cloud/deploy-to-cloud-run-using-gitlab-ci-e056685b8eeb

and I change to my needs the .gitlab-ci and the cloudbuild.yaml

After several tryouts, I finally manage to set all the Roles, Permissions and Service Accounts. But no luck building my docker file into the Container Registry or Artifact.

this is my failure log from gitlab log:

Currently I'm facing the issue: