Is the Docker --expose now supported in Terraform?

Before going back testing Terraform again I have the following question.
When I tested last time I could not use Terraform as it would always expose an external port even though I don’t want that.

Old example:

In Docker I can use the –expose to avoid exposing the Docker Container

docker run -dit --name jogy-apache --expose 80 -v “$PWD”:/usr/local/apache2/htdocs/ httpd:2.4

CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS
ccd8cb4aa068 httpd:2.4 “httpd-foreground” 8 hours ago Up 8 hours 80/tcp

But if use a Terraform template with ports on for internal and none for external

resource “docker_container” “nginx01” {
name = “nginx01”
image = “${docker_image.nginx.latest}”
ports {
internal = 80
}
volumes {
container_path = “/usr/share/nginx/html”
host_path = “/home/jogy/www”
read_only = true
}
}

The end result …

CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
021200107f0c bedece1f06cc “nginx -g 'daemon of…” 6 days ago Up 6 days 443/tcp, 0.0.0.0:32768->80/tcp nginx01

Ports
ports is a block within the configuration that can be repeated to specify the port mappings of the container. Each ports block supports the following:

internal - (Required, int) Port within the container.
external - (Optional, int) Port exposed out of the container. If not given a free random port >= 32768 will be used.
ip - (Optional, string) IP address/mask that can access this port, default to 0.0.0.0
protocol - (Optional, string) Protocol that can be used over this port, defaults to tcp.

Does anyone know if this has changed? If so, I will kick of another test of Terraform.