No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

What’s the directory structure? Can you tell us how those things are located in reference to each other:
• Pulumi.yaml
• source file (the one containing the code snippet mentioned above)
• Dockerfile
How do you run pulumi CLI (from what directory) on the top of that?

if you’re on linux-like platform, try to run `tree` in the command line :slightly_smiling_face:

I’ve never used `docker` package but I have a strange feeling that using `../` might be not allowed :thinking_face:

or if it is, it might be an issue with “current working directory”, relative paths can be resolved based on:
• Pulumi.yaml (project file)
• current working directory in which you run `pulumi up`
• the actual file containing the rel path

This is my structure:

project/
 -ops(Folder) -&gt; here is the Pulumi.yaml
    --resources(Folder) -&gt; here is the actual pulumi docker code
    --index.ts
    --Pulumi.yaml
DockerFile -&gt; the docker file we need tu build


DockerFile is inside project root folder.

We run `pulumi up` command inside `ops` folder.

So that’s why we are using `../` as context and `../DockerFile` as it’s actually the relative path (one up from ops, where we run the command)

we already tried with one more directory but it didn’t work. (Expecting to use resources as the current path from pulumi)

We also logged the `__dirname` and `pwd` and everything points to `ops` folder, where we are standing.

can you try to move the Dockerfile to `ops` folder, change the code accordingly and run `pulumi up` again to see if the error persists?

it’s possible that the package cannot move outside of the pulumi project dir (that’s just my blind guess, assuming you haven’t done any silly mistake)

let me try to quickly check sth in my machine

We found the issue, and it’s not related to the dockerfile (as the error says)

It’s related to some dependency (elastic search) not being able to be resolved…….

We are going to investigate further and upload an issue to pulumi github

Thanks a lot <@U0288KYUB7C>! :party-pizza:

I feel like I did nothing to help you but I’m glad to hear you managed to find the root cause :slightly_smiling_face:

please post here a link to the issue when you report it :thank-you: