could not connect to unix:///run/user/1000/buildkit/buildkitd.sock

[Tusenka]

Contributing guidelines and issue reporting guide

• I've read the contributing guidelines and wholeheartedly agree. I've also read the issue reporting guide.

Well-formed report checklist

• I have found a bug that the documentation does not mention anything about my problem
• I have found a bug that there are no open or closed issues that are related to my problem
• I have provided version/information about my environment and done my best to provide a reproducer

Description of bug

Bug description

Error when running the exactle version after v0.28.0 the pipe drops with the error.

could not connect to unix:///run/user/1000/buildkit/buildkitd.sock

It works fine on the version v0.28.0.

Reproduction

Run gitlab:

build_image:
  stage: build
  image: moby/buildkit:v0.28.0-rootless
  tags: [kubernetes, yandex-cloud]
  variables:
    BUILDKITD_FLAGS: --oci-worker-no-process-sandbox
    CACHE_IMAGE: $CI_REGISTRY_IMAGE:cache
  before_script:
    - mkdir -p ~/.docker
    - echo "{\"auths\":{\"$CI_REGISTRY\":{\"username\":\"$CI_REGISTRY_USER\",\"password\":\"$CI_REGISTRY_PASSWORD\"}}}" > ~/.docker/config.json
  script:
    - >
      buildctl-daemonless.sh build
      --frontend dockerfile.v0
      --local context=.
      --local dockerfile=.
      --opt platform=linux/amd64
      --export-cache type=registry,ref=$CACHE_IMAGE
      --import-cache type=registry,ref=$CACHE_IMAGE
      --output type=image,name=$CI_REGISTRY_IMAGE:$CI_COMMIT_SHA,push=true

Version information

v0.28.1

Terminal_output

$ buildctl-daemonless.sh build --frontend dockerfile.v0 --local context=. --local dockerfile=. --opt platform=linux/amd64 --export-cache type=registry,ref=$CACHE_IMAGE --import-cache type=registry,ref=$CACHE_IMAGE --output type=image,name=$CI_REGISTRY_IMAGE:$CI_COMMIT_SHA,push=true
could not connect to unix:///run/user/1000/buildkit/buildkitd.sock after 10 trials

[jirimoravcik]

Hello, so you're saying v0.28.0 works properly, but when you upgrade to v0.28.1, your pipeline breaks? Given that v0.28.1 is a security release, I really don't see anything that could break your pipeline.

[AkihiroSuda]

Any log output?

buildkit/examples/buildctl-daemonless/buildctl-daemonless.sh

Lines 48 to 49 in 1154c7e

	echo >&2 "========== log =========="
	cat >&2 $tmp/log

[Tusenka]

v0.28.1 is a security release

jirimoravcik, thank you. For my outside point of view access to (unix:///run/user/1000/buildkit/buildkitd.sock) doesn't look like that frontend files outside buildKit state ...

[Tusenka]

Any log output?

buildkit/examples/buildctl-daemonless/buildctl-daemonless.sh

Lines 48 to 49 in 1154c7e
echo >&2 "========== log =========="
cat >&2 $tmp/log

AkihiroSuda, Thank you for the answer. Could you help me - where to see $tmp/log output? There no log output from the script. No "========== log ==========" line.