SWA Login: libsecret-1.so.0: cannot open shared object file: No such file or directory

Describe the bug Receiving error when running a swa login command on linux from within docker image / dev container.

To Reproduce Steps to reproduce the behavior:

1. Run az login to initialize azure credentials
2. Run az account set -s {subscriptionId} to set default subscription
3. Run swa login --subscription-id {subscriptionId} --resource-group {resourceGroupName} --tenant-id {tenantId} --app-name {appName}

Expected behavior SWA login command should succeed without error to allow for subsequent commands to deploy.

Actual behavior Receive the following error Failed to setup project: libsecret-1.so.0: cannot open shared object file: No such file or directory

Screenshots

Desktop (please complete the following information):

• OS: Linux, vscode dev container mcr.microsoft.com/vscode/devcontainers/base:0-bullseye

Additional context Works as expected on Windows

When passing in the --no-use-keychain it runs me through a fresh azure login and works as expected.

[wbreza]

@manekinekko We ended up using option 3 from your list where we manually grab the deployment token and pass it through to the swa deploy command instead of making a call to swa login. All is now working as expected.

[manekinekko]

A little bit of context

When using swa login, the flag --use-keychain is enabled by default because we encrypt and store your credentials in your native Keychain (aka. the built-in password manager of your operating system). This operation depends on a system dependency called libsecret. If your system doesn’t come bundled libsecret (most systems do provide it by default), you will then encounter the error in the OP.

Why do I need to swa login?

In order to be able to automatically deploy your app to your Azure Static Web Apps instance, we need a Deployment Token. To automate that operation and avoid asking the users to manually find that deployment token, which can take several steps, we provide a built-in and convenient option to do that: swa login.

How to avoid this issue?

In order to avoid this issue, you have a few options:

1. Manually install libsecret by adding it to your Docker image or your system (recommended)
2. Disable Keychain access using --no-use-keychain. Doing so won’t store and remember your credentials anymore, and you will have to interactively log in again each time you run swa login
3. Manually provide the Deployment Token for your current project (see SWA CLI docs). You will also need to provide --app-name and --resource-group-name
4. Manually provide --client-id, --client-secret, --app-name and --resource-group-name.