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

SST V3 Pulumi error: operation not supported #1089

Open
joaohbracht opened this issue Sep 18, 2024 · 3 comments
Open

SST V3 Pulumi error: operation not supported #1089

joaohbracht opened this issue Sep 18, 2024 · 3 comments
Assignees

Comments

@joaohbracht
Copy link

joaohbracht commented Sep 18, 2024

@ updating.................

    pulumi:pulumi:Stack sst-production  error: an unhandled error occurred: operation not supported
    pulumi:pulumi:Stack sst-production **failed** 1 error
Diagnostics:
  pulumi:pulumi:Stack (sst-production):
    error: an unhandled error occurred: operation not supported

Resources:

Duration: 1s

Into sst.log I have this:

level=ERROR msg="stack run failed" error="failed to run update: exit status 255\ncode: 255\nstdout: Updating (production):\n@ updating.................\n\n    pulumi:pulumi:Stack sst-production  error: an unhandled error occurred: operation not supported\n    pulumi:pulumi:Stack sst-production **failed** 1 error\nDiagnostics:\n  pulumi:pulumi:Stack (sst-production):\n    error: an unhandled error occurred: operation not supported\n\nResources:\n\nDuration: 1s\n\n\nstderr: \n"
@jayair
Copy link
Contributor

jayair commented Sep 21, 2024

Can you tell me a bit more about this? What's in your sst config?

@jayair jayair self-assigned this Sep 21, 2024
@HenryOwenz
Copy link

HenryOwenz commented Sep 21, 2024

Can you tell me a bit more about this? What's in your sst config?

Hello. I am not the original poster but i'm having a similar issue.
I am trying out sst for the first time.

Issue: 'sst dev' fails with "operation not supported" on Windows WSL2

Environment

  • Operating Systems:
    • Windows 11 (WSL2 - Ubuntu)
  • Next.js version: 14.2.13
  • SST version: 3.1.31
  • AWS Profile: sandbox1
  • Node.js version: v22.9.0

Steps to Reproduce

  1. Run the following commands on Windows WSL2:

    npx create-next-app@latest aws-nextjs
    cd aws-nextjs
    npx sst@latest init
  2. Modify sst.config.ts to include the following code:

    /// <reference path="./.sst/platform/config.d.ts" />
    
    export default $config({
      app(input) {
        return {
          providers: {
            aws: {
              profile: "sandbox1"
            }
          },
          name: "aws-nextjs",
          removal: input?.stage === "production" ? "retain" : "remove",
          home: "aws",
        };
      },
      async run() {
        new sst.aws.Nextjs("MyWeb");
      },
    });
  3. Run npx sst dev.

Expected Behavior

According to the SST documentation, the process should complete successfully, and I should be able to click on "MyWeb" in the SST sidebar to open my Next.js app in the browser.

Actual Behavior

The SST sidebar begins the deployment process but fails during the deployment stage with the following error logs:

Pulumi Log

Updating (solis):
@ updating.................

    pulumi:pulumi:Stack aws-nextjs-solis  error: an unhandled error occurred: operation not supported
    pulumi:pulumi:Stack aws-nextjs-solis **failed** 1 error
Diagnostics:
  pulumi:pulumi:Stack (aws-nextjs-solis):
    error: an unhandled error occurred: operation not supported

Resources:

Duration: 1s

Event Log

{"sequence":0,"timestamp":1726922211,"preludeEvent":{"config":{"aws:defaultTags":"{\"tags\":{\"sst:app\":\"aws-nextjs\",\"sst:stage\":\"solis\"}}","aws:region":"us-east-1"}},"Error":null}
{"sequence":1,"timestamp":1726922211,"diagnosticEvent":{"prefix":"error: ","message":"an unhandled error occurred: operation not supported\n","color":"never","severity":"error"},"Error":null}
{"sequence":2,"timestamp":1726922211,"summaryEvent":{"maybeCorrupt":false,"durationSeconds":1,"resourceChanges":{},"PolicyPacks":{}},"Error":null}
{"sequence":3,"timestamp":1726922211,"cancelEvent":{},"Error":null}

SST Log

err="stack run had errors"

Additional Context

  • Some resources were created in the AWS sandbox1 account, such as sst-asset-<id> and sst-state-<id>, which seemed to contain the expected files. I could not find any other related resource that was deployed other than the 2 buckets.
  • The SST Next.js Quickstart Guide was followed without deviation.

Any guidance or insights into what might be going wrong here would be greatly appreciated. Please let me know if I can provide further information or run additional tests to help resolve this issue. I'm currently getting ready to try to reproduce this on a standalone linux machine (not WSL), and also mac OS. maybe the issue is specific to WSL?

Lasly, I am aware of this note on 'https://sst.dev/docs/reference/cli': The CLI currently supports macOS, Linux, and WSL. Windows support is coming soon. I wonder if you literally mean 'WSL Version 1' only. Or if you mean WSL1 & WSL 2 compatibility.

@thdxr thdxr assigned thdxr and unassigned jayair Sep 23, 2024
@PaulOliverppt
Copy link

PaulOliverppt commented Sep 23, 2024

I've had this issue if my project is hosted in the windows system vs the WSL 2 system.

When I hosted the project in the WSL 2 system instead (eg. /home/user/project) it worked without issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants