azure / vscode-remote-try-bicep Goto Github PK

I realize the issue this caused for me is my fault since I just copied and pasted the devcontainer.json without fully comprehending.

However, when this dev container is running, it hijacks the communication of all Azure Function local development (since by default they run on port 7071). Took me a while to realize this was at fault.

I have removed the forwarded port from my devcontainer.json and everything appears to be working fine.

Hello,

I ran Bicep Dev container on latest VS code failed,the screenshot is below,any suggestions?

Thanks,
Teo

Hi!

Perhaps you are already aware that there is a Developer Container definition for bicep present here: https://github.com/microsoft/vscode-dev-containers/tree/master/containers/azure-bicep

The microsoft/vscode-dev-containers repo is the one that feed VS Code with baked official and community Dev Containers definitions.

To avoid fragmentation shouldn't both definition be merged?