Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ENGDOCS-2451 #22117

Merged
merged 8 commits into from
Mar 6, 2025
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
fix links
  • Loading branch information
aevesdocker committed Feb 28, 2025
commit 58431cde0bc33f18c495774222008926fa8b96b6
2 changes: 1 addition & 1 deletion content/get-started/workshop/05_persisting_data.md
Original file line number Diff line number Diff line change
@@ -114,7 +114,7 @@ You can create the volume and start the container using the CLI or Docker Deskto
> ```
>
> For more details about Git Bash's syntax differences, see
> [Working with Git Bash](/desktop/troubleshoot-and-support/troubleshoot/topics/#working-with-git-bash).
> [Working with Git Bash](/desktop/troubleshoot-and-support/troubleshoot/topics/#issue-docker-commands-failing-in-git-bash).


{{< /tab >}}
2 changes: 1 addition & 1 deletion content/guides/language-translation.md
Original file line number Diff line number Diff line change
@@ -315,7 +315,7 @@ To run the application using Docker:
>
> 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/#avoid-unexpected-syntax-errors-use-unix-style-line-endings-for-files-in-containers).
> 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/#Issue-Unexpected-syntax-errors-use-Unix-style-line endings-for-files-in-containers).

You will see the following in your console after the container starts.

2 changes: 1 addition & 1 deletion content/guides/named-entity-recognition.md
Original file line number Diff line number Diff line change
@@ -318,7 +318,7 @@ To run the application using Docker:
>
> 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/#avoid-unexpected-syntax-errors-use-unix-style-line-endings-for-files-in-containers).
> 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/#Issue-Unexpected-syntax-errors-use-Unix-style-line endings-for-files-in-containers).

You will see the following in your console after the container starts.

2 changes: 1 addition & 1 deletion content/guides/sentiment-analysis.md
Original file line number Diff line number Diff line change
@@ -331,7 +331,7 @@ To run the application using Docker:
>
> 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/#avoid-unexpected-syntax-errors-use-unix-style-line-endings-for-files-in-containers).
> 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/#Issue-Unexpected-syntax-errors-use-Unix-style-line endings-for-files-in-containers).

You will see the following in your console after the container starts.

2 changes: 1 addition & 1 deletion content/guides/text-classification.md
Original file line number Diff line number Diff line change
@@ -390,7 +390,7 @@ To run the application using Docker:
>
> 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/#avoid-unexpected-syntax-errors-use-unix-style-line-endings-for-files-in-containers).
> 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/#Issue-Unexpected-syntax-errors-use-Unix-style-line endings-for-files-in-containers).

You will see the following in your console after the container starts.

2 changes: 1 addition & 1 deletion content/guides/text-summarization.md
Original file line number Diff line number Diff line change
@@ -324,7 +324,7 @@ To run the application using Docker:
>
> 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/#avoid-unexpected-syntax-errors-use-unix-style-line-endings-for-files-in-containers).
> 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/#Issue-Unexpected-syntax-errors-use-Unix-style-line endings-for-files-in-containers).

You will see the following in your console after the container starts.

Loading
Oops, something went wrong.