Open reubano opened 1 year ago
Some additional info. I've figured out that, unlike docker, Azure Containers can't mount a file, they can only mount directories. That means you can't do something like VolumeMountArgs(mount_path="/etc/nginx/nginx.conf", name="nginx-config", read_only=True)
. You would have to do VolumeMountArgs(mount_path="/etc/nginx", name="nginx", read_only=True)
and then either upload nginx.conf
via the az
CLI or use a secret volume to store the b64 encoded file contents.
A good idea would be for pulumi to check if you are trying to mount a file and bail out via error vs waiting 30m for azure to timeout.
Hi @reubano, thank you for the update and the detailed initial report! Do I understand correctly that the problem does not occur when you mount a directory?
We'll take your idea of a local check into account, thank you!
What happened?
I'm creating an Azure ContainerGroup with associated StorageAccount and FileShares. I've found that the
pulumi up
command often times out. However, runningpulumi refresh
and thenpulumi up
again works.When it fails I get the following errors
or
Also, the
publicIP
export is sometimes not present in the output.Expected Behavior
No errors. Or at least an indication as to why rerunning
pulumi up
makes it work.Steps to reproduce
Pulumi.yaml
Pulumi.dev.yaml
__main__.py
Output of
pulumi about
Additional context
No response
Contributing
Vote on this issue by adding a 👍 reaction. To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).