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

pulumi-deployment-config.png

It looks like the deployment previews are running in Pulumi Cloud, but not being reported back to GitHub via the GitHub App

This might be because it's erroring during setup, when it attempts to pull the image

```1
 Preparing environment 
2
 Pulling container image "<http://ghcr.io/meltano/pulumi:latest|ghcr.io/meltano/pulumi:latest>" 
3
 image pull failed; retrying 
4
 Pulling container image "<http://ghcr.io/meltano/pulumi:latest|ghcr.io/meltano/pulumi:latest>" 
5
 image pull failed; retrying 
6
 Pulling container image "<http://ghcr.io/meltano/pulumi:latest|ghcr.io/meltano/pulumi:latest>" 
7
 image pull failed; retrying 
8
 Pulling container image "<http://ghcr.io/meltano/pulumi:latest|ghcr.io/meltano/pulumi:latest>" 
9
 image pull failed; retrying 
10
 Pulling container image "<http://ghcr.io/meltano/pulumi:latest|ghcr.io/meltano/pulumi:latest>" 
11
 giving up 
12
 pulling image: retry limit reached ```

<@U84HBHXS8> Do you know why this might be failing? The registry is the GitHub registry, <http://ghcr.io|ghcr.io>, the repository username is a GitHub username, and the repository password is a GitHub PAT with read permission for packages. I've tested out these credentials locally by logging in via `docker login` then pulling the image, and it worked fine.

The image is only available for `linux/amd64` - could that be the problem?

<@U045FPK11FU> you may have seen the status page update, there is a wide spread AWS outage related to ec2 and networking that is impacting Deployments and anything networking related that happens within the runs (downloading dependencies, source code, etc).

<@UQ8K13T7X> I see the status has been updated to "All Systems Operational", but I'm not seeing any deployments being made, or comments being left by the GitHub app

Screen Shot 2023-09-19 at 1.34.39 PM.png

Are you able to click to deploy to initiate a preview on the stack? Just want to isolate the issue.

There are some other things that could prevent a PR preview from running:
• an incorrectly configured path filter
• if the PR was opened by a github org member who membership is set to `private`

fyi I'm working through this in a DM with <@U01BSQWRZFA>

We had already ruled out the path filter problem (by removing the path filters), and the GitHub org member problem (by using an org member who had used Pulumi Deployments yesterday without issue)

I was able to do a manual deployment, but the automatic ones didn't work. Changes to the tracked branch in GitHub do nothing. Nothing shows up in the "Activity" tab

Mitch suggested disabling the custom image, and it caused it to run automatically when the next commit was pushed to the tracked branch

Then I re-enabled the custom image, and it worked again automatically

So maybe there's a bug where it requires at least one run to occur without a custom image before a custom image can be used?

Hm, that does sound strange. If you have a repro, would you mind opening a bug so we can investigate? <https://github.com/pulumi/pulumi-cloud-requests/issues/new/choose>

I’ll put together a repro and open an issue.