Running the Application: Container Execution, Testing, and Summary

this case) is sent to the Docker daemon to enable the build. It includes all the files and subdirectories in the specified directory. For more details, see the [docker build CLI reference](/reference/cli/docker/buildx/build/). Docker outputs several logs to your console as it builds the image. You'll see it download and install the dependencies. Depending on your network connection, this may take several minutes. Docker does have a caching feature, so subsequent builds can be faster. The console will return to the prompt when it's complete. 2. Run the image as a container. In a terminal, run the following command. ```console $ docker run -it basic-nlp 05_language_translation.py ``` The following is a break down of the command: - `docker run`: This is the primary command used to run a new container from a Docker image. - `-it`: This is a combination of two options: - `-i` or `--interactive`: This keeps the standard input (STDIN) open even if not attached. It lets the container remain running in the foreground and be interactive. - `-t` or `--tty`: This allocates a pseudo-TTY, essentially simulating a terminal, like a command prompt or a shell. It's what lets you interact with the application inside the container. - `basic-nlp`: This specifies the name of the Docker image to use for creating the container. In this case, it's the image named `basic-nlp` that you created with the `docker build` command. - `05_language_translation.py`: This is the script you want to run inside the Docker container. It gets passed to the `entrypoint.sh` script, which runs it when the container starts. For more details, see the [docker run CLI reference](/reference/cli/docker/container/run/). > [!NOTE] > > For Windows users, you may get an error when running the container. Verify > that the line endings in the `entrypoint.sh` are `LF` (`\n`) and not `CRLF` (`\r\n`), > then rebuild the image. For more details, see [Avoid unexpected syntax errors, use Unix style line endings for files in containers](/desktop/troubleshoot-and-support/troubleshoot/topics/#Unexpected-syntax-errors-use-Unix-style-line endings-for-files-in-containers). You will see the following in your console after the container starts. ```console Enter the text for translation (type 'exit' to end): ``` 3. Test the application. Enter some text to get the text summarization. ```console Enter the text for translation (type 'exit' to end): Hello, how are you doing? Original Text: Hello, how are you doing? Translated Text: Bonjour comment allez-vous? ``` ## Summary In this guide, you learned how to build and run a language translation application. You learned how to build the application using Python with Googletrans, and then set up the environment and run the application using Docker. Related information: - [Docker CLI reference](/reference/cli/docker/) - [Dockerfile reference](/reference/dockerfile/) - [Googletrans](https://github.com/ssut/py-googletrans) - [Python documentation](https://docs.python.org/3/) ## Next steps Explore more [natural language processing guides](./_index.md).

This section details how to run the built Docker image as a container, explaining the 'docker run' command and its options such as `-it` for interactive mode and tty allocation. It also explains that 'basic-nlp' specifies the Docker image to use and '05_language_translation.py' is the script to run inside the container. A note addresses a potential error for Windows users regarding line endings in the 'entrypoint.sh' file. The section proceeds with testing the application by providing input and observing the translated output. Finally, it summarizes the guide's content, covering the building and running of a language translation application using Python with Googletrans and Docker, and provides links to relevant documentation and further learning resources.