I tried to outsmart the pipelines and setup the buildx CLI plugin like
pipelines:
default:
- step:
services: [docker]
script:
- wget --no-verbose https: - chmod a+x ~/.docker/cli-plugins/docker-buildx
- docker buildx create --use
- docker buildx build . --pull --cache-from registry.my.org/foo/bar --build-arg BUILDKIT_INLINE_CACHE=1 --progress=plain
but this fails with
WARNING: No output specified for docker-container driver. Build result will only remain in the build cache. To push result image into registry use --push or to load image into docker use --load
#1 [internal] booting buildkit
#1 pulling image moby/buildkit:buildx-stable-1
#1 pulling image moby/buildkit:buildx-stable-1 2.3s done
#1 creating container buildx_buildkit_busy_haibt0 done
#1 ERROR: Error response from daemon: authorization denied by plugin pipelines: --privileged=true is not allowed
------
> [internal] booting buildkit:
------
error: Error response from daemon: authorization denied by plugin pipelines: --privileged=true is not allowed
Fat chance.
I never requested a privileged container, though. Am I doing something wrong?
Hi 257cb8fcc776 ,
As discussed in the comment, we have released a variable BITBUCKET_SSH_KEY_FILE to the provide the path to the ssh private key file.
Please refer our documentation for more details.
Regards,
Jayant