I use a docker service in my pipelines to build images. I see that it starts the daemon without the containerd snapshotter:
msg="Docker daemon" commit=e63daec containerd-snapshotter=false storage-driver=overlay2 version=25.0.5
It runs this image according to logs:
docker : docker-public.packages.atlassian.com/sox/atlassian/bitbucket-pipelines-docker-daemon@sha256:6b9b4a11c1fb311cfff394be811dda4bf4268793a2d43e9b5f6eedff3ae31c42
Is there an alternate image available, or a config I can set, to enable containerd snapshotter, to allow me to build images in the pipeline with attestations for vulnerability scans?
Hey @Erik Rask
Welcome to the community!
I believe this is not possible if you are using the Bitbucket cloud pipeline. Perhaps look into Bitbucket runner - Self hosted as it offer more control over the Docker daemon.
Regards,
Syahrul
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.