Issue when using transparent network with sql container images

[richmccloud]

I have been working with the latest sqlexpress and sql vNext container images on docker hub and have identified what appears to be an issue only when using a transparent network (2 issues actually):
1 - minor issue - ip address is not visible when using docker inspect but I can ping the container by name successfully
2 - only when using transparent network, I receive "login failed for user sa;' when attempting to conntect to the sql instance. I can use the exact same docker run command (minus --network) and I can login and access sql just fine.

I am using the run command specified on docker hub, just added the --network=lan (and removed -p 1433:1433). Also confirmed that the password is complex (cap, lowercase, number and special character, 8 characters long):
docker run -d --network=lan -e sa_password=<SA_PASSWORD> -e ACCEPT_EULA=Y -v C:/temp/:C:/temp/ -e attach_dbs="[{'dbName':'SampleDb','dbFiles':['C:\temp\sampledb.mdf','C:\temp\sampledb_log.ldf']}]" microsoft/mssql-server-windows

[richmccloud]

Removing the option to run in detached mode seems to resolve the problem. Are detached mode and transparent network incompatible? Thanks

[twright-msft]

Firewall?

[Koubek]

Maybe you need to --expose the port 1433 (actually you have correctly removed the port mapping which is incompatible with transparent network type; instead you need to expose the port or I suppose you have to do so).