Closed samahatw closed 11 months ago
Same here on ubuntu 22.04 using snap installation.
I'm also seeing this on an M1 MBP, with Rancher Desktop:
❯ circleci local execute
Fetching latest build environment...
Docker image digest: sha256:c3be9fb94fdf377e6a8d508fc0b833bb18a99a36a2d7d89a8e39c7701838f701
WARNING: The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested
Error: failed to start event processor: failed to compute task config: failed to read config file: read /tmp/local_build_config.yml: is a directory
I'm not sure if this is related to the container being linux/amd64 and the host being M1, or if it's a different problem entirely.
$ docker version
Client:
Version: 20.10.17-rd
API version: 1.41
Go version: go1.17.11
Git commit: c2e4e01
Built: Fri Jul 22 18:32:57 2022
OS/Arch: darwin/arm64
Context: default
Experimental: true
Server:
Engine:
Version: 20.10.16
API version: 1.41 (minimum version 1.12)
Go version: go1.18.4
Git commit: f756502055d2e36a84f2068e6620bea5ecf09058
Built: Thu Jul 21 18:43:18 2022
OS/Arch: linux/arm64
Experimental: false
containerd:
Version: v1.6.6
GitCommit: 10c12954828e7c7c9b6e0ea9b0c02b01407d3ae1
runc:
Version: 1.1.2
GitCommit: a916309fff0f838eb94e928713dbc3c0d0ac7aa4
docker-init:
Version: 0.19.0
GitCommit:
$ circleci version
0.1.20500+e042377 (homebrew)
Same here. Using M1 MBP also. Using colima for container runtime.
% circleci local execute
Fetching latest build environment...
Docker image digest: sha256:8c7e8c77261c5c6227c1ee27f95f902bd046d42c8c849039d8144942ba6c12e7
WARNING: The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested
Error: failed to start event processor: failed to compute task config: failed to read config file: read /tmp/local_build_config.yml: is a directory
% circleci version
0.1.22675+19bba9e (homebrew)
% docker version
Client: Docker Engine - Community
Version: 20.10.21
API version: 1.41
Go version: go1.19.3
Git commit: baeda1f82a
Built: Tue Oct 25 17:53:02 2022
OS/Arch: darwin/arm64
Context: colima
Experimental: true
Server:
Engine:
Version: 20.10.18
API version: 1.41 (minimum version 1.12)
Go version: go1.18.6
Git commit: e42327a6d3c55ceda3bd5475be7aae6036d02db3
Built: Sun Sep 11 07:10:00 2022
OS/Arch: linux/arm64
Experimental: false
containerd:
Version: v1.6.8
GitCommit: 9cd3357b7fd7218e4aec3eae239db1f68a5a6ec6
runc:
Version: 1.1.4
GitCommit: 5fd4c4d144137e991c4acebb2146ab1483a97925
docker-init:
Version: 0.19.0
GitCommit:
% colima version
colima version 0.4.6
git commit: 10377f3a20c2b0f7196ad5944264b69f048a3d40
runtime: docker
arch: aarch64
client: v20.10.21
server: v20.10.18
Also unable to launch local circleci build using Rancher on MacOS with same error. This is a bigger problem now due to recent licensing to Docker Desktop (which prohibit use in corporate environment unless enterprise license is purchased). Any solutions?
Related colima issue: https://github.com/abiosoft/colima/issues/571
I think I at least know what's happening. Installed using snap on Ubuntu 22.04.
Docker sometimes can't mount files from /tmp
, which at least seems to be the case for installs using snap, and the confusing failure mode is that it just creates a directory instead of failing.
Do not install docker and circleci using snap. Use one of the other installation methods. That solved the problem for me.
Hi @samahatw do you still have this issue ?
I am M1 mac
circleci local execute build Fetching latest build environment...
Error: failed to start event processor: failed to compute task config: failed to read config file: read /tmp/local_build_config.yml: is a directory
circleci version 0.1.26837+b104265 (homebrew)
Thanks everyone for reporting this issue and contributing in the comments!
The underlying problem comes from Lima not accepting /tmp
as a mount for its VMs, as it considers it a "system path" similar to /etc
or /usr
.. Any container distribution using Lima will face this issue, including colima and Rancher Desktop.
We're currently at work on this, and we seem to have found a solution in #967. We're still working on adding some tests and checks to make sure this is reliable and future-proof, and we'll release it as soon as we can.
Version 0.1.29560 just released.
It contains a fix for this issue. Define circleci
's temporary directory:
circleci local execute --temp-dir /path/to/your/temp/dir
~/.circleci/cli.yml
), setting temp_dir: '/path/to/your/temp/dir'
This should fix the issue for colima, Rancher Desktop and other Lima-based container distributions.
Version 0.1.29560 just released.
this is not fixed for wsl2, but using --temp-dir
worked around it thanks!
Meta:
CircleCI CLI Version: 0.1.18678+c3ad28b (homebrew)
Operating System: macOS Monterey 12.3.1
CircleCI CLI Diagnostic:
Current behavior:
I'm trying to run the simplest example (foo_ci). I got an error when I try to execute locally,
circleci local execute
.Expected behavior:
Run the pipeline locally.
When did this begin / Was this previously working?:
It never worked.
Additional Information:
Macbook Pro M1 (arm64). Using colima to run docker engine.