-
Notifications
You must be signed in to change notification settings - Fork 777
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
Running Bicep from Docker image #13392
Comments
All right I've done more digging in the past few days, this looks like it may be a specific CLI issue as when I run the command from my local I'm having the exact same problem output, which the local machine handles gracefully but forces the container runtime to exit.
In the meantime if anyone has any thoughts or recommendations I'd be greatly appreciative! |
Closing this issue and opened new issue on Azure Cli repository. Azure/azure-cli#28448 |
Hey. I am also facing this issue with the exact same error:
|
Hello @Jasstkn and thanks for the reminder, meant to post an update on how I ended up solving this riddle.
A couple of points:
Hopefully some of this helps you in your resolution! Best, |
Bicep version
0.25.53
Describe the bug
I am attempting to run Bicep from a Node app that instantiates a cli instance. When the app runs from the source code on my machine (Apple M1 Pro) I have no issues, however, once in a container the same processes throw any number of errors. Most recently I'm getting:
prior was:
To Reproduce
cli command executed:
bicep file:
Docker file:
Additional context
The error above is not the only error I've dealt with, many previously surrounding the well-known issue with arm64 architecture. Been hacking at this for a few days now and curious if there are others who have had this same issue or perhaps I'm working uphill combining Docker and Bicep with known limitations. I've also built this image on specifically amd64 chipsets and run into similar problems.
The text was updated successfully, but these errors were encountered: