碼上快樂

相關內容    簡體    繁體

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

本文轉載自   查看原文   2019-06-03 18:56   2158 

golang docker build 制作完進項后運行報錯

出現該問題的原因是編譯的環境和運行的環境不同，可能有動態庫的依賴

１．默認go使用靜態鏈接，在docker的golang環境中默認是使用動態編譯。

２．如果想使用docker編譯+alpine部署，可以通過禁用cgoCGO_ENABLED=0來解決。

３．如果要使用cgo可以通過go build --ldflags "-extldflags -static" 來讓gcc使用靜態編譯。

 

 

 

參考: https://yryz.net/post/golang-docker-alpine-start-panic.html

 


免責聲明！

本站轉載的文章為個人學習借鑒使用，本站對版權不負任何法律責任。如果侵犯了您的隱私權益，請聯系本站郵箱yoyou2525@163.com刪除。



猜您在找 standard_init_linux.go:178: exec user process caused "no such file or directory" 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 容器啟動腳本報錯：exec user process caused "no such file or directory" 運行docker容器時報錯 exec user process caused "no such file or directory" docker exec 無法進入容器 OCI runtime exec failed、container_linux.go:348: starting container process caused "process_linux.go:78: starting setns process caused \"fork/exec /proc/self/exe: no such file docker OCI runtime exec failed: exec failed: container_linux.go:349: starting container process caused "exec: \"bash\": executable file not found in $PATH": unknown 查看容器ip時報錯“OCI runtime exec failed: exec failed: container_linux.go:380: starting container process caused: exec: "ip": executable file not found in $PATH: unknown” OCI runtime create failed: container_linux.go:349: starting container process caused "exec: "bash": executable file not found in $PATH": unknown 【Docker錯誤】starting container process caused "exec: \"/bin/bash\": stat /bin/bash: no such file or directory": unknown OCI runtime create failed: container_linux.go:380: starting container process caused: exec:
 
粵ICP備18138465號   © 2018-2025 CODEPRJ.COM