Paul
Reputation: 449
Azure container instance behave differently that local container
I have a strange situation that i would like to share with you. I started container recently and wand to have Azure DevOps agent running on container.
- On my windows 10 laptop , i can instanciate a Linux container and everything run & execute well (using WSL)
- On a Ubuntu VM running an Azure, the same container run well and execute well
- However the same container in Azure Container instance failed and for unknow reason i get the following error:
- Generating browser application bundles (phase: setup)... /bin/sh: 1: wslpath: not found 01 12 2022 14:55:59.933:ERROR [config]: Error in config file! Error: Command failed: wslpath -w "/usr/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin" /bin/sh: 1: wslpath: not found
When i see wsl i think about Windows Subsystem Linux but i am not sure. I really do not understand why ACI behave like that with that error. I always thought that container should behave the same wherever it runs. Did you experience it ? Any idea are welcome. Regards
Upvotes: 1
Views: 184
Answers (0)
Related Questions
- Same exact docker image, services within running container have two different behaviors
- Azure lists no containers but returns information on a given name
- Why docker container acts differently?
- Why is Azure double-pulling my image & "losing track" of the resulting container?
- Containers with docker-compose have different behavior depending on machine where they are executed
- Running commands in azure container instance after container running
- Azure Container Instance apparently keeps running after Stop or Delete
- az container exec when using Docker compose
- Azure container instance is failing again and again
- Interacting with a container in Azure Container Instances