Deployment fails when deploying with the '-PrivateACR' about ipam HOT 4 CLOSED

FYI this has been fixed in the latest release v3.2.0 and was addressed in #279.

Hope everything is working better for you now!

from ipam.

Hi @RegExpresso, the long story short is that the apt-get update process changed and now displays some Unicode characters that don't work so well in Windows machines and causes this issue.

This is being fixed in the next version which is coming out shortly, but here's a workaround for now:

1. Go to Settings
2. Click Time and language
3. Click Language and region
4. Click Administrative language settings
5. Click Change system locale
6. In the Region Settings dialog, select the Beta: Use Unicode UTF-8 for worldwide language support checkbox
7. Click OK to save any changes
8. Click Apply
9. Reboot your PC for the change to take effect

There will also be a second step you'll need to perform due to an issue I found in the current deployment script where it sets the listening port of the container to 80, which isn't supported.

To build a container with the proper listening port, re-deploy the container by executing these commands from the root directory of the ipam folder:

1. az login
2. az account set -s <Subscription ID Where IPAM is Deployed>
3. az acr build -r <Private ACR Name> -t ipam:latest -f ./Dockerfile .

NOTE: These instructions can also be found here on our docs page.

That should properly build the container and push it to the ACR. After that restart your App Service and give it a few minutes to pull down the new container.

Hope that helps, and the new code should fix all of this very shortly!

from ipam.

Works like a charm, much appreciated @DCMattyG!!

from ipam.

Much appriciated @DCMattyG!!

from ipam.