trivy | Find vulnerabilities, misconfigurations, secrets, SBOM in containers, Kubernetes, code repositories, | Continuous Deployment library

I solved the problem. It took the following: Connect to DB container Execute the following commands in psql:

The problem is that you're telling GitLab to run the Pipeline within a container with the image trivy image, which I suppose it's a custom Dockerfile using aquasec/trivy as base image.

If you haven't installed the Docker CLI in your custom image, there is no reason for it to be there.

The first question to solve is, which tools are available within your trivy container you are using, do you have tar available inside or not.

the command for extracting via tar is quiet simple tar -xzf .

GitLab CI is normally already checking out your repository, so the files should be already in place, and there is no need for special care.

aquasec/trivy is distributed as a multi-platform image. The first one in your list is from the manifest list itself, and the second digest is for your specific platform:

As ridiculous as it sounds. It turned out that my network was blocking download. Switching to tethered internet from my mobile device solved the problem.

Security concerns aside, you need to provide the full path to your executable:

Replace trivy in the script with the results of which trivy from a shell

are you using kubeadm? if you are using kubeadm; you can follow the next steps:

1. Delete slaves nodes

   kubecl delete node k8sslave1

2. From the slaves' nodes, execute:

   kubeadm reset

3. Then you need to join the slaves' nodes to the cluster, in the master node execute:

   token=$(kubeadm token generate)

   kubeadm token create $token --ttl 2h --print-join-command

4. Paste the output of the command in the slaves nodes.

   kubectl join ...

5. Review that the nodes are join to the cluster and the new state is Ready.

   ubuntu@kube-master:~$ kubectl get nodes