This message was deleted.

Hey @refined-pilot-45584, do you also have the

go

binary somewhere in your

PATH

for Pulumi to find it?

100% on the money; Was weird as my SSH session and VSCode Server sessions had different configurations. Resolved now but your suggestion was exactly the fix. It wasn’t looking at the right Paths.

Does the file

/tmp/pulumi-go.4092750539

exist? Is it an executable?

@limited-rainbow-51650 Yeah I had seen this post. It’s interesting I have tried both the build configuration options and also remounting my /tmp folder but to no avail. That said I have also noticed something weird the mentioned .go executable file never actually appears in the /tmp folder or in the build config folder if I add one. Further more Pulumi up / Pulumi New don’t seem to be making my .Pulumi folder anymore…

Have you tired setting "buildTarget" to a path inside the project folder (like "./projexe")?

Hey @echoing-dinner-19531 I have; Two things on this. I would hope to avoid having to hard code it in this way. However when I add the build it still doesn’t work. Secondly another strange thing is I get the error: “Sorry, could not create stack ‘dev’: stack ‘dev’ already exists” but specifically when running Pulumi new in a en empty folder. One thing I have noticed that might be “problematic” whats the max supported version of GO for Pulumi?

Secondly another strange thing is I get the error: “Sorry, could not create stack ‘dev’: stack ‘dev’ already exists” but specifically when running Pulumi new in a en empty folder.

That might be an odd error message based on the project already existing. What does

pulumi stack ls ---all

show?

whats the max supported version of GO for Pulumi?

We test with 1.19 and 1.20, and our support policy is for any version currently "in support" from upstream (i.e https://go.dev/doc/devel/release#policy)

pulumi stack ls ---all

shows all the stacks. However I am not 100% sure where they are located, some of them appear in app.pulumi.com and some do not. So I think at different times pulumi login has been set to local. . I am also checking a few things about the GO version now. I am not sure if It’s Go related but I am using v1.21 I will try with a different version probably 1.19 to see if it’s that.

ls --all

should only show from one place, it can't query the service and the local backend at the same time. We haven't tested 1.21 yet so that could be an issue, if you find out what's wrong with it we can probably fix it up given we're gonna be supporting 1.21 once it's officially released anyway.

@echoing-dinner-19531 could you think of any reason why the

pulumi up

command would get a permission denied error given that the file configured in the runtime args is being created by the same

pulumi up

command:

runtime:
  name: go
  options:
    buildTarget: ./build/project

Maybe execute bit permissions, I'm not sure we're explicit about setting that.

ls -l ./build/project

and see what that says. You could also try running with verbose logs (

-v10 --logflow --logtostderr

) to see if that logs out any more information about what's going on.

Yeah Okay I am going to try the verbose logging. Additionally. Small question. When someone runs

pulumi new gcp-go

Are you logged in to the local filesystem `pulumi login file://`<file://I|?> That'll be stack state ".pulumi" folder.

Did you ever end up solving the issue? @refined-pilot-45584 I'm experiencing a similar error

Hey @clean-zoo-67541 yes; Actually I did. It was a combination of multiple things. Firstly. I was building out a template; Which was the plan. But the template was consuming a module. Both the Module and the Template had main functions. I was trying to repurpose the main.go file for both the module and the template functions and this didn’t work so i separated them out. Module (no main function). Template (main function) in main.go Then when I run the pulumi new cli command the template is built but it doesn’t try to build the module but rather consumes it.

Thank you so much for the detailed response! that's perfect

Sorry it took so long. Let me know if this resolves the problem for you.