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

pulumi package get-schema docker calls docker #11014

Closed
iwahbe opened this issue Oct 13, 2022 · 4 comments · Fixed by #11015
Closed

pulumi package get-schema docker calls docker #11014

iwahbe opened this issue Oct 13, 2022 · 4 comments · Fixed by #11015
Assignees
Labels
kind/bug Some behavior is incorrect or out of spec resolution/fixed This issue was fixed
Milestone

Comments

@iwahbe
Copy link
Member

iwahbe commented Oct 13, 2022

What happened?

While attempting to debug an issue with pulumi-docker, pulumi package get-schema docker was called. Instead of retrieving the schema from the already downloaded docker provider, it seemingly called the docker CLI.

Steps to reproduce

Run pulumi package get-schema docker

Expected Behavior

The docker schema is written to stdout.

Actual Behavior

docker: '127.0.0.1:59789' is not a docker command.

See 'docker --help'

error: could not read plugin [docker] stdout: EOF

:point_uis written to standard error.

Output of pulumi about

CLI          
Version      3.42.0-dev.0
Go Version   go1.19
Go Compiler  gc

Host     
OS       darwin
Version  12.6
Arch     x86_64

Additional context

@Zaid-Ajaj found the bug, I (@iwahbe) confirmed that it was cross-platform and reproducible.

Contributing

Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

@iwahbe iwahbe added kind/bug Some behavior is incorrect or out of spec needs-triage Needs attention from the triage team labels Oct 13, 2022
@Frassle
Copy link
Member

Frassle commented Oct 13, 2022

os.Stat looks at PATH, we use that to decided if the string passed to us is a plugin file to invoke directly or a plugin name. "docker" is a file on PATH so we try to invoke it directly.

@iwahbe
Copy link
Member Author

iwahbe commented Oct 13, 2022

os.Stat looks at PATH, we use that to decided if the string passed to us is a plugin file to invoke directly or a plugin name. "docker" is a file on PATH so we try to invoke it directly.

Here is the funny thing. aws is also on my path, but pulumi package get-schema aws works as expected.

There even both symlinks:

$ ls $(which aws) $(which docker)
lrwxr-xr-x 30 iwahbe   12 Oct 20:02 /usr/local/bin/aws -> ../Cellar/awscli/2.8.2/bin/aws*
lrwxr-xr-x 54 root     16 Aug  2021 /usr/local/bin/docker -> /Applications/Docker.app/Contents/Resources/bin/docker*

@iwahbe
Copy link
Member Author

iwahbe commented Oct 13, 2022

In pulumi/pulumi, where I happened to be while testing, there is a directory called docker. There is not a directory called aws. That causes the problem. If there is a file, we error as intended.

@iwahbe iwahbe self-assigned this Oct 13, 2022
@iwahbe iwahbe removed the needs-triage Needs attention from the triage team label Oct 13, 2022
@iwahbe iwahbe added this to the 0.79 milestone Oct 13, 2022
@Frassle
Copy link
Member

Frassle commented Oct 13, 2022

Oh I must have hit exactly the same setup! I got docker wondered how the hell looked at the man pages and they said stat would search path, but I guess the stat mode go uses elides that and we just hit a folder as well instead.

Maybe we should require a slash to indicate a path? ./docker

bors bot added a commit that referenced this issue Oct 13, 2022
11015: Require a path separator for path based binaries. r=iwahbe a=iwahbe

This allows us to distinguish between ./myProvider (execute the binary at path) and myProvider (execute the installed plugin called myProvider).

<!--- 
Thanks so much for your contribution! If this is your first time contributing, please ensure that you have read the [CONTRIBUTING](https://github.com/pulumi/pulumi/blob/master/CONTRIBUTING.md) documentation.
-->

# Description

<!--- Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. -->

Fixes #11014

## Checklist

<!--- Please provide details if the checkbox below is to be left unchecked. -->
- [ ] I have added tests that prove my fix is effective or that my feature works
<!--- 
User-facing changes require a CHANGELOG entry.
-->
- [X] I have run `make changelog` and committed the `changelog/pending/<file>` documenting my change
<!--
If the change(s) in this PR is a modification of an existing call to the Pulumi Service,
then the service should honor older versions of the CLI where this change would not exist.
You must then bump the API version in /pkg/backend/httpstate/client/api.go, as well as add
it to the service.
-->
- [ ] Yes, there are changes in this PR that warrants bumping the Pulumi Service API version
  <!-- `@Pulumi` employees: If yes, you must submit corresponding changes in the service repo. -->


Co-authored-by: Ian Wahbe <ian@wahbe.com>
@bors bors bot closed this as completed in b4bf3dd Oct 13, 2022
@pulumi-bot pulumi-bot added the resolution/fixed This issue was fixed label Oct 13, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Some behavior is incorrect or out of spec resolution/fixed This issue was fixed
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants