If there were another container using the same image, the destroy step wouldįail.The PRO importer is not something I am proud of - it was written to facilitate the Import of basic PRO Data only (Polylines, Sets, Surfaces and Alignments), and for that purpose it is OK, however for Corridors I do not recommend using the Importer at all as you will see this type of issue because the Importer basically slices up the Corridor into "Cross Sections" and imports them as Templates and then interprets the surface model between the templates - and this is why you are seeing the surface model differences between the two - the Exported File is fine and if you opened that in Terramodel (A better test) you will see that it is fine, it is just the Imported Version into TBC that is incorrect because of the way that the Corridor Model is imported. The container, the image will be removed from Docker as well as the container. Tip: Since you added the image to your Terraform configuration as well as docker_image.nginx: Destruction complete after 0s Destroy complete! Resources: 2 destroyed. docker_container.web: Destruction complete after 1s docker_image.nginx: Destroying. Enter a value: yes docker_container.web: Destroying. Do you really want to destroy all resources? Terraform will destroy all your managed infrastructure, as shown above. The container's configuration using Terraform before finally destroying it when Next, you will import it into a new Terraform workspace. In this tutorial, first you will create a Docker container with the Docker CLI.