Closed FelixZY closed 2 months ago
This also occurs on Alpine Linux 3.19 after doing 'sudo apk add libsecret'
See https://github.com/adrianhall/swa-alpine-test for repro - just add sudo apk add libsecret before running.
Ref: #858
Can confirm this is still an issue. The solution in the linked thread, installing libsecrets, does not seem to solve the problem in a devcontainer.
This is fixed in v2.0.0 when using azure CLI login:
/workspaces/swa-alpine-test/swa-react-demo $ npx swa login --resource-group adhal-swa-demo --app-name swa-react-demo
(node:5360) ExperimentalWarning: Importing JSON modules is an experimental feature and might change at any time
(Use `node --trace-warnings ...` to show where the warning was created)
Welcome to Azure Static Web Apps CLI (2.0.0)
Using configuration "swa-react-demo" from file:
/workspaces/swa-alpine-test/swa-react-demo/swa-cli.config.json
Checking Azure session...
✔ Successfully logged into Azure!
✔ Saved project credentials in .env file.
✔ Successfully setup project!
/workspaces/swa-alpine-test/swa-react-demo $
v2.0.0 is out this week; if you can't wait, load from azure/static-web-apps-cli#main.
Describe the bug
SWA CLI commands fail with
Cannot spawn a message bus without a machine-id
when executing in a debian (mcr.microsoft.com/devcontainers/base:bullseye
) devcontainer.To Reproduce Steps to reproduce the behavior:
mcr.microsoft.com/devcontainers/base:bullseye
swa login
orswa deploy
(note: you may need to installlibsecret-1-dev
)Expected behavior Successful operation; no error.
Desktop (please complete the following information):
Additional context
Some solutions suggest exposing the host computer's
/var/lib/dbus/machine-id
to the devcontainer. I would prefer not doing so as that does not seem like a cross-platform solution.