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 is the best way to get the docker build output from a pulumi app that is building a docker.Image? I feel like I'm missing something obvious.

You can't. If you want it (and IMO, even if you don't want it), you can move the Docker build phase outside of Pulumi. Have Pulumi be dependent on the built Docker image.

<@U012UJTT55M> In the past, I would just find the error running `docker build .` to see what is erroring, but this time `docker build` works but the pulumi docker build is segfaulting...
```docker:index:Image  latest                creating (42s).    runtime/cgo: gcc: signal: segmentation fault (core dumped)```

Tracking down the segfault is a moot point if the pulumi docker provider isn't able to expose build errors.

The provider itself may have options to help debug. However, building the image is a significant part of the CI process, and rolling it into CD (or.deployment of any type) is, in my experience, likely to bring more disadvantages than advantages.

It is analogous to creating your NPM package or jar file when deploying. It just doesn't fit.

Hm, this seems unexpected to me. I’ll check on it to be sure, as it seems this should be possible somehow.

image.png

If you're using Pulumi Cloud, you can see it under Diagnostics, for example here:

What about us self-hosted peasants? :stuck_out_tongue:

Is there an option to print it as diagnostics?
```❯
awe psvc pulumi up --skip-preview
Updating (svc-usw2):
     Type                      Name                        Status           Info
     pulumi:pulumi:Stack       aws-argocd-pulumi-svc-usw2
     └─ awsx:ecr:Image         argocd-pulumi-cmp
 ~      └─ docker:index:Image  latest                      updated (4s)     [diff: ~build]

Resources:
    ~ 1 updated
    6 unchanged

Duration: 9s```

There is hope :slightly_smiling_face:  -- you can use `--non-interactive` for one

So like `pulumi up --yes --non-interactive`

I don't know if there's a way to isolate the diagnostic output though -- I can look into that