![]() gitattributes file with the following line: *. sh files right in the repo by adding the. If you own a repo or contribute to it, set mandatory LF line endings for. Reset the repo using this (don't forget to save your changes): git rm -cached -r. The solution for me was to disable git's automatic conversion: This meant that the shebang didn't work because instead of looking for /bin/bash, it was looking for /bin/bash\r. But when the repository was checked out on a windows machine, git decided to try and be clever and replace the line endings in the files with windows line endings (\r\n). In my case the git repository had an entry point script with Unix line endings (\n). But actually the problem was Windows line endings. I was tearing my hair out with an issue very similar to this. Standard_init_linux.go:175: exec user process caused "no such file or directory" Removing intermediate container 7434f052178f Step 6 : ENTRYPOINT /docker-entrypoint.sh Please correct me if I misunderstood something or elaborate a little bite more where I should find the docker-entrypoint.sh file etc. Hence, I assume it should be copied to the right directory by the Dockerfile of the images I used (e.g. Removing intermediate container 251395c4790f I don't create a docker-entrypoint.sh file myself. ![]() Step 5 : RUN chmod +x /docker-entrypoint.sh The docker-compose.yml has restart: unless-stopped specified by the way. Step 3 : COPY vaultConfig.json /vault/config The issue Im having is that when I run docker-compose build and then docker-compose up, I can see the script runs, but something in it causes the container to fail and restart itself - the script then runs again, and the cycle continues. ![]() Sending build context to Docker daemon 126 kB Why so? Doesn't Work $ docker build -t gilani/trollo. The start of the script had the line /bin/bash, and during execution of docker-compose up (after successfully building with docker-compose build, the. ![]() My ENTRYPOINT script doesn't execute and throws standard_init_linux.go:175: exec user process caused "no such file or directory". I came here with a similar issue while troubleshooting my attempt to build a Dockerfile 'entry point' ( entrypoint.sh) bash shell script (to be executed within the. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |