码上欢乐
相关内容   简体   繁体

standard_init_linux.go:207: exec user process caused "no such file or directory"

本文转载自  查看原文  2019-08-11 20:18  1915    kubernetes/ ASP.NET Core

运行docker容器异常中止，使用docker logs CONTAINER_ID查看异常信息如下：standard_init_linux.go:207: exec user process caused "no such file or directory" 

这是dos字符与unix字符的问题，我使用的windows 环境里 visual studio 编写的 shell 脚本 默认是以DOS文本格式来创建的，所以才导致这样的问题。

解决方法：

使用 Notepad++.执行一个批量的替换 :

  1. Menu: Search -> Find in Files...
  2. Directory = the directory you want to be converted to Unix format, recursively. E.g., C:\MyDir
  3. Find what = \r\n
  4. Replace with = \n
  5. Search Mode = Extended
  6. Press "Replace in Files"


免责声明！

本站转载的文章为个人学习借鉴使用，本站对版权不负任何法律责任。如果侵犯了您的隐私权益，请联系本站邮箱yoyou2525@163.com删除。



猜您在找 standard_init_linux.go:178: exec user process caused "no such file or directory" standard_init_linux.go:178: exec user process caused "no such file or directory" windows上启动docker容器报错：standard_init_linux.go:211: exec user process caused “no such file or directory” - Docker standard_init_linux.go:211: exec user process caused "no such file or direct 问题 通过dockerfile构建时报standard_init_linux.go:228: exec user process caused: exec format error docker制作镜像文件问题standard_init_linux.go:208: exec user process caused "no such file or direct docker运行容器报错standard_init_linux.go:211: exec user process caused “exec format error“的可能解决办法 docker - 进入容器报错：OCI runtime exec failed: exec failed: container_linux.go:370: starting container process caused: exec: "/bin/bash": stat /bin/bash: no such file or directory: unknown OCI runtime exec failed: exec failed: container_linux.go:380: starting container process caused: exec: "/bin/bash": stat /bin/bash: no such file or directory: unknown 自定义容器启动脚本报错：exec user process caused "no such file or directory"
 
粤ICP备18138465号  © 2018-2025 CODEPRJ.COM