From 9ae16c5adf2385aca0c01e6678c1da13edcb61a4 Mon Sep 17 00:00:00 2001 From: Nicole Rappe Date: Tue, 7 May 2024 13:43:19 -0600 Subject: [PATCH] Update Docker & Kubernetes/Docker/Custom Containers/Container Development.md --- .../Docker/Custom Containers/Container Development.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/Docker & Kubernetes/Docker/Custom Containers/Container Development.md b/Docker & Kubernetes/Docker/Custom Containers/Container Development.md index e1222fe..3b1cb8d 100644 --- a/Docker & Kubernetes/Docker/Custom Containers/Container Development.md +++ b/Docker & Kubernetes/Docker/Custom Containers/Container Development.md @@ -65,5 +65,8 @@ At this point, we need to build the dockerfile, which takes all of the changes a - In the dropdown menu that appears, enter `git.bunny-lab.io/container-registry/git-repo-updater:latest` - You can confirm if it was successful by navigating to the [Gitea Container Webpage](https://git.bunny-lab.io/container-registry/-/packages/container/git-repo-updater/latest) and seeing if it says "**Published Now**" or "**Published 1 Minute Ago**" +!!! warning "CLRF End of Line Sequences" + When you are editing files in the container's repository, you need to ensure that Visual Studio Code is editing that file in "**LF**" mode and not "**CRLF**". You can find this toggle at the bottom-right of the VSCode window. Simply clicking on the letters "**CRLF**" will let you toggle the file to "**LF**". If you do not make this change, the container will misunderstand the dockerfile and/or scripts inside of the container and have runtime errors. + ## Deploy the Container You can now use the `.env` file along with the `docker-compose.yml` file inside of Portainer to deploy a stack using the container you just built / updated. \ No newline at end of file