8000 [bug] macOS Catalina: kubectl-pxc cannot be opened because the developer cannot be verified · Issue #108 · portworx/pxc · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
This repository was archived by the owner on Mar 26, 2025. It is now read-only.

[bug] macOS Catalina: kubectl-pxc cannot be opened because the developer cannot be verified #108

Open
rodrigc opened this issue Feb 4, 2020 · 4 comments
Open

[bug] macOS Catalina: kubectl-pxc cannot be opened because the developer cannot be verified #108

rodrigc opened this issue Feb 4, 2020 · 4 comments
Labels
bug Something isn't working

Comments

@rodrigc
Copy link
rodrigc commented Feb 4, 2020 •
edited
Loading

Describe the bug

When using the kubectl-pxc binary on macOS, I get an error when trying to open it:

image

Version

  • 0.23.0
  • macOS Catalina 10.15.2

To Reproduce

  1. Extract pxc-v0.23.0.darwin.amd64.tar.gz
  2. Run kubectl-pxc

Expected behavior
kubectl-pxc should run without error

Actual behavior
I get a security dialog error.

Additional Information

Workaround:

On macOS, follow the steps mentioned here:

http://osxdaily.com/2016/09/27/allow-apps-from-anywhere-macos-gatekeeper/

and run:

sudo spctl --master-disable

Other projects have encountered this here
@rodrigc rodrigc added the bug Something isn't working label Feb 4, 2020
@rodrigc rodrigc changed the title [bug] [bug] macOS Catalina: kubectl-pxc cannot be opened because the developer cannot be verified Feb 4, 2020
@lpabon
Copy link
Contributor
lpabon commented Feb 4, 2020

Seems like all open source products are suffering from this. See

hashicorp/terraform#23033

@lpabon
Copy link
Contributor
lpabon commented Feb 4, 2020 •
edited
Loading

oh, wow: https://developer.apple.com/videos/play/wwdc2019/703

Golang: golang/go#35459

Time to move to Windows or Linux!

@lpabon
Copy link
Contributor
lpabon commented Feb 4, 2020

Maybe try this? helm/helm#6615 (comment)

@rodrigc
Copy link
Author
rodrigc commented Feb 4, 2020

I would say for now this is not worth fixing, until a clear approach in the open source community emerges that we can follow.
For now, I've run sudo spctl --master-disable which is not advisable, but this affects me on other open source projects that I download on my Mac.
xattr -d is the approach mentioned here: helm/helm#6615 (comment)
which I haven't tried.

I think just mentioning these workarounds on macOS is good enough for now.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@rodrigc @lpabon
0