web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics NAV (Archived)

Publishing the Docker Ports but it published ports are mapped to 0.0.0.0

(0) ShareShare
ReportReport
Posted on by 3,967

Hi,

I've created Microsoft Dynamics Business Central on container. I've used the following powershell scripts

$additionalParameters = @("--publish 8080:8080",

"--publish 443:443", 

"--publish 7046-7049:7046-7049",
"--env publicFileSharePort=8080",
"--env RemovePasswordKeyFile=N"
)
$params = @{ "enableSymbolLoading" = $true
"licensefile" = "<LICENESE FILE URL>" }
$auth = "NavUserPassword"

New-NavContainer -accept_eula @params -containerName NAV -includeCSide -credential cfadmin -additionalParameters $additionalParameters -alwaysPull -imageName "navinsider.azurecr.io/dynamics-nav:11.0.21063.0-finus" -useSSL

The container gets created and I can access it locally. I'm trying to publish the ports but when I view the container ports it gives

PS C:\demo> docker port <ID>
7047/tcp -> 0.0.0.0:7047
443/tcp -> 0.0.0.0:443
7046/tcp -> 0.0.0.0:7046
7048/tcp -> 0.0.0.0:7048
7049/tcp -> 0.0.0.0:7049
8080/tcp -> 0.0.0.0:8080

Kindly guide. 
Thanks

*This post is locked for comments

I have the same question (0)
  • Suggested answer
    Stefano Demiliani Profile Picture
    37,166 Most Valuable Professional on at

    Why 0.0.0.0? Has the container an IP address assigned?

  • Olister Rumao Profile Picture
    3,967 on at

    Yes, the IP gets assigned to the container. Using that IP the container is accessible as well.

    I think this issue might be due to some firewall settings but I do not to undersand where to check as my VM is hosted on Azure.

    I also tried changing the image name in setting.ps located at C:\DEMO folder in the VM that is created through the http://aka.ms/navdeveloperpreviewext link. There changing the image name allows me to setup and accessible from other machines as well.

    So, I'm trying to make the same on my VM using powershell.

  • Suggested answer
    Stefano Demiliani Profile Picture
    37,166 Most Valuable Professional on at

    Ok. By default Docker containers can make connections to the outside world, but the outside world cannot connect to containers.

    When you invoke docker run you can use either -p IP:host_port:container_port or -p IP::port to specify the external interface for one particular binding.

    docs.docker.com/.../binding

  • Olister Rumao Profile Picture
    3,967 on at

    I've used

    $additionalParameters = @("--publish 8080:8080",

    "--publish 443:443",

    "--publish 7046-7049:7046-7049",

    "--env publicFileSharePort=8080",

    "--env RemovePasswordKeyFile=N"

    ) variable  is used in New-NavContainer. This is already defined in standard powershell scripts.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > 🔒一 Microsoft Dynamics NAV (Archived)

#1
HoangNam Profile Picture

HoangNam 7

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans