Uploading BC Developer License to a container hosted in Azure Container Instance.

(0) Share

Report

Posted on by Olister Rumao

3,967

Hi,

I've created a container on Azure following https://community.dynamics.com/nav/b/andreysnavblog/archive/2018/04/02/quot-server-less-quot-dynamics365-business-central.
I wanted to upload the development licence to the BC. Earlier it was possible with the help of NavContainerHelper module.
Thanks.

*This post is locked for comments

I have the same question (0)

All responses (31)

Answers (7)

Verified answer

Andrey Baludin 3,941 on at

Like (0)

Report

My suggestion is to redeploy container like this

az container create --name navbc --image "microsoft/dynamics-nav:12.0.21229.0" --resource-group bc --os-type Windows --cpu 2 --memory 3 --environment-variables ACCEPT_EULA=Y USESSL=N LICENSEFILE=c:\run\my\license.flf --ip-address public --port 80 443 8080

One question - is c:\run\my\license.flf would be enable from Azure?

I guess you need to put license file somewhere in cloud to access with url.

Was this reply helpful? Yes No
Olister Rumao 3,967 on at

Like (1)

Report

Yes Andrey using it directly from dropbox via sharing should resolve the issue.

Kindly modify your blog (community.dynamics.com/.../quot-server-less-quot-dynamics365-business-central) and also include port 7049 without which i couldn't connect VSCode to the container.

Thanks

Was this reply helpful? Yes No
Verified answer

Andrey Baludin 3,941 on at

Like (0)

Report

Yes, I've set it in my test but forgot to set in blog. Thanks, it's edited!

By the way, if you need to set some other parameters to container, you can find them in Freddy's blog:

blogs.msdn.microsoft.com/.../multiple-ways-to-run-a-nav-on-docker-image

Parameters which he sets with docker after "-e" in azure can be set as --environment-variables.

Was this reply helpful? Yes No
Verified answer

CDsilva 4,188 on at

Like (1)

Report

Hi Andry,

In your post you have included 6 ports while creating container but container allows max 5 ports. I included 80 443 7049 8080 then it worked.

Was this reply helpful? Yes No
jgaztanaga 225 on at

Like (0)

Report
Hi andrey:

I'm, Running this command:

az container create --name MDBC --image "microsoft/dynamics-nav:12.0.21229.0" --resource-group NAVBC --os-type Windows --cpu 2 --memory 3 --environment-variables ACCEPT_EULA=Y USESSL=N LICENSEFILE=D :\Base\Para Upgrade\6045219-desa2018.flf --ip-address public --port 80 443 8080 7049

And I have this error:

Incorrectly formatted environment settings. Argument values should be in the format a=b c=d

Any clue about his? May be any sintactic error??

Thank ypu very much, any hint will be really appreciated

Was this reply helpful? Yes No
Suggested answer

Andrey Baludin 3,941 on at

Like (0)

Report

Hi!

I guess, problem is on license file path (space in Para Upgrade).

I'm thinking it should looks like LICENSEFILE=D:\Base\"Para Upgrade"\6045219-desa2018.flf

Or just put it in some simple folder like C:\Temp.

But i'll predict a problems because azure can't see your D drive. You need to put license file somewhere in cloud. Dropbox for example.

Also I advise you to use another image name (actual): microsoft/bcsandbox

Was this reply helpful? Yes No
jgaztanaga 225 on at

Like (0)

Report

Hi!

First of all, thnak tyou for your quick ansewr. I've solved it putting in one folder in C. But now, when I run the "az container logs --resource-group navbc --name mdbc" command, I can see this error:

Why can be this happening? The license file is a development license for NAV2018, may be that could be the problem, I don't know...

AS you can see, this are my first steps with NAV BC....

Thank you again!!

Was this reply helpful? Yes No
Andrey Baludin 3,941 on at

Like (0)

Report

Can't see error image. But I also use dev license for NAV2018 and everything is ok.

Was this reply helpful? Yes No
Verified answer

CDsilva 4,188 on at

Like (0)

Report

Can you post your screenshot again? Its not visible

Was this reply helpful? Yes No
jgaztanaga 225 on at

Like (0)

Report

Sorry, in the preview I thought that the image was OK.

Was this reply helpful? Yes No