Image will not deploy on Azure as stated in Blog

[mmenzie]

Hello,
I have followed the blog for deploying this image in Azure multiple times and it fails every time. I opened a ticket with Microsoft Azure Tech support and got an email back stating that the tech followed the guide as well and it failed for him too. He suspects that there is an issue with the image as deploying other images using the same methodology works. I have tried multiple times to post on the authors blog but he moderates comments and my comments are never posted and replies never returned

[pglombardo]

Hi @mmenzie - can you detail the problem you are hitting and on what step? I've never tried the Azure deploy myself (hence the link to the external blog) but maybe I can give it a shot. Let me know here how far you got and what the issue was.

[mmenzie]

Hello Peter, all the steps seem to be ok there are no errors until it tries to deploy. the blog says it should take 4 to 5 minutes buy mine will deploy for much much longer than that and then fail with an error of "conflict". i opened aticket with Microsoft Tech support thinking it was an issue on Azure and here is what i got from them: Hello Micheal, Thanks for contacting Microsoft Support. My name is <tech name redacted> and I am the Support Engineer who will be working with you on support request 2103160040008213. You can reach me using the contact information in my signature. Per the case description, we failed to depoly an ACI following the blog post: PWPush | Host your own using Azure Containers – Part 1 | Getting Started – Tame The Cloud <https://tamethe.cloud/pwpush-host-your-own-using-azure-containers/> *[Business Impact] If the issue is affecting your business, please let us know.* *Current findings:* 1. I reviewed the backend logs and I found there was a deployment operation at 2021-03-16T19:27:12Z, which ends at 2021-03-16T20:03:14Z, with the message: “Subscription deployment is timeout, state is 'Failed'.”; 2. based on the deployment logs, during the deployment, the container status was always waiting, and the reason was “waiting to run”. It indicates that the container was unable to start; 3. I reproduced the issue from my side following the blog post, and I found the same failure. However, when I choosed another images with the same configration I found the deployment was succeeded. It indicates that deployment failure was due to the image “pglombardo/pwpush-ephemeral”; *Next action:* Since the blog and image are both from 3rd party, and we are unable to understand how the image was built, could you please kindly reach to the 3rd party or community to get the right image and then re-try the deployment? i also asked him what image he used when he said he chose a different image and it was successful and he told me it was just another software, not pwpush, and he was just verifing that deploying docker images actually was working. i too, tried a BitWarden docker image and it deployed to Azure following the same steps without issue. so i can kind of understand why the tech is thinking it may be the image but not 100% sure thanks for replying to me too, by the way

…

On Thu, Mar 25, 2021 at 3:27 PM Peter Giacomo Lombardo < ***@***.***> wrote: Hi @mmenzie <https://github.com/mmenzie> - can you detail the problem you are hitting and on what step? I've never tried the Azure deploy myself (hence the link to the external blog) but maybe I can give it a shot. Let me know here how far you got and what the issue was. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#175 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ARRRTPGE6ESA7CY3P2UC7NDTFOFC7ANCNFSM4ZXKAWQA> .

-- Michael Menzie Server Administrator Orange County Community College 845-341-4564. Ext 4564 115 South Street Middletown, NY 10940

[pglombardo]

Ok that helps. Maybe someone in the community can chime in but if not I'll try it out myself soon. I'll post back here once I have some info.

[mmenzie]

well it seems the Microsoft tech continued to try things and he found something that worked. i tried it as well and was able to deploy pwpush in Azure Containers. here is what he told me and it worked... I changed the ACI size from “1 vcpu, 1.5GiB memory” to “4vcpu, 8GiB memory”

…

On Thu, Mar 25, 2021 at 6:26 PM Peter Giacomo Lombardo < ***@***.***> wrote: Ok that helps. Maybe someone in the community can chime in but if not I'll try it out myself soon. I'll post back here once I have some info. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#175 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ARRRTPATTT5YOWDMTBJQJ2TTFO2C5ANCNFSM4ZXKAWQA> .

[pglombardo]

I suppose that is good news although it seems like a lot. pwpush.com is run on Heroku with 512mb allocated but there, the app is running without the container. If the extra resources are an issue, let me know. I still hope to try out Azure myself eventually.

[pglombardo]

I will close this issue for now and use it as a reference for any other Azure users going forward. Thanks for reporting!