https://community.cloudera.com/t5/Support-Questions/We-got-an-error-quot-standard-init-linux-go-207-exec-user/m-p/238639#M200450 <P><A rel="noopener noreferrer noopener noreferrer" href="http://@chetan%20gehlot" target="_blank"><EM>@chetan gehlot</EM></A></P><P><EM>The problem was indeed that Docker image files are architecture specific (at least the default ones). So a Docker file built on Intel will only work on Intel, and a Docker file build for Arm32 will only work for Arm32.</EM></P><P><EM>It seems there are ways to build an Arm build on an Intel device but that would still leave you with distributing two separate images. And if you have a physical Arm device it is much easier to build an Arm image directly on an Arm device.</EM></P><P><EM>You also need to make sure your base image supports your architecture, but the official one has now been built as multi-arch images so this is not usually a problem.</EM></P><P><EM>Another related problem and solution: <CODE>standard_init_linux.go:207</CODE></EM></P><P><EM>In case your entry point is bash script check whether it contains correct shebang, something like that:</EM></P><PRE><EM><CODE>#!/usr/bin/env bash </CODE></EM> <EM><CODE>make -f /app/makefile $@ </CODE></EM></PRE><P><EM>Also, have a look at <A href="https://stackoverflow.com/questions/51508150/standard-init-linux-go190-exec-user-process-caused-no-such-file-or-directory">standard_init_linux.go:190: exec user process caused "no such file or directory" - Docker</A>, might be related too.</EM></P> Fri, 19 Apr 2019 13:12:53 GMT Shelton 2019-04-19T13:12:53Z