Deploy fails at redis container app
See original GitHub issuePlease provide us with the following information:
This issue is for a: (mark with an x
)
- [X ] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)
Minimal steps to reproduce
azd up
Any log messages given by the failure
Deployment Error Details: ContainerAppOperationError: Failed to provision revision for container app ‘redis’. Error details: Operation expired.
Issue Analytics
- State:
- Created 3 months ago
- Comments:5
Top Results From Across the Web
Docker-compose deploying redis but app.js refuses ...
1 Answer 1 ... The node application is expecting the redis to be on the localhost, which it is not. You can provide...
Read more >Fails to connect to redis, when running inside of docker ...
My application is a microservice, which connects to a redis database, which is running inside of docker. However, I can not connect to...
Read more >Deploying a pod running a local app and a redis container
Greetings. I'm currently trying to run a pod containing my local user api and a redis container as the first needs to connect...
Read more >redis container failed to connect - SCIM bridge deployment ...
Basically, we used the guide from 1Password github to set up our SCIM bridge and it seems like the redis container cannot start...
Read more >Unable to pull remote image for multi-container web ...
The web app using this deployment setup has been working flawlessly for several months (it's a multi-container web application deployed from my ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I was able to resolve this by reverting back to the latest available version included in the documentation. Next, because the
service
andserviceBind
properties were not recognized, I commented them out and was able to successfully deploy the template. Not sure what these properties do exactly.I changed container-app.bicep as follows:
@Jeroen-VdB thank you for the work around you proposed, it also solved the same problem for me