Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue using the junit plugin on osx #81

Closed
remi-debette opened this issue Mar 27, 2020 · 2 comments
Closed

Issue using the junit plugin on osx #81

remi-debette opened this issue Mar 27, 2020 · 2 comments
Labels

Comments

@remi-debette
Copy link

Hi
First, thank you for the great tool which allows to test our pipelines on local.

Running the tool installed from brew on osx, I encountered an issue that seems to be linked with the peculiar status of the platform.

When running the sample pipeline of the plugin: junit-annotate, I see the following error happening:

 bk local run .buildkite/pipeline.integration_tests.yml
(...)

--- :junit: Processing the junits
docker: Error response from daemon: Mounts denied: 
The path /var/folders/kf/fsdklxv57_v6kq5ydjxpj6g00000gp/T/buildkite-plugins-670558647/github-com-buildkite-plugins-junit-annotate-buildkite-plugin-v1-7-0/ruby
is not shared from OS X and is not known to Docker.
You can configure shared paths from Docker -> Preferences... -> File Sharing.
See https://docs.docker.com/docker-for-mac/osxfs/#namespaces for more info.
.
ERRO[0000] error waiting for container: context canceled 
🚨 Error: The command exited with status 125

Apparently, when trying to mount such a folder on a mac, one would need to prefix /var with /private and use instead /private/var according to this comment

Is this a problem of the plugin or of the bk local agent?

@pzeballos
Copy link

Hey! Sorry for the delay! If you are still having issues, can you send your build details to [email protected]? 🙏 Thanks!

@mcncl
Copy link
Contributor

mcncl commented Sep 29, 2024

👋 We don't currently support a local run command in the new CLI version (3.x.x). As you've seen, there are some complexities around having a local run command in the CLI and we're looking at other methods of providing this functionality.

@mcncl mcncl closed this as not planned Won't fix, can't repro, duplicate, stale Sep 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants