Support Questions
Find answers, ask questions, and share your expertise
Announcements
Alert: Welcome to the Unified Cloudera Community. Former HCC members be sure to read and learn how to activate your account here.

We got an error "standard_init_linux.go:207: exec user process caused "exec format error"".

Highlighted

We got an error "standard_init_linux.go:207: exec user process caused "exec format error"".

New Contributor

We got an error "standard_init_linux.go:207: exec user process caused "exec format error"". When I run the script.

2 REPLIES 2

Re: We got an error "standard_init_linux.go:207: exec user process caused "exec format error"".

Mentor

@chetan gehlot

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.

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.

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.

Another related problem and solution: standard_init_linux.go:207

In case your entry point is bash script check whether it contains correct shebang, something like that:

#!/usr/bin/env bash 
make -f /app/makefile $@

Also, have a look at standard_init_linux.go:190: exec user process caused "no such file or directory" - Docker, might be related too.

Re: We got an error "standard_init_linux.go:207: exec user process caused "exec format error"".

New Contributor

I run this script



#!/usr/bin/env bash

#This script downloads HDP sandbox along with their proxy docker container

set -x


# CAN EDIT THESE VALUES

registry="hortonworks"

name="sandbox-hdp"

version="3.0.1"

proxyName="sandbox-proxy"

proxyVersion="1.0"

flavor="hdp"


# NO EDITS BEYOND THIS LINE

# housekeeping

echo $flavor > sandbox-flavor



# create necessary folders for nginx and copy over our rule generation script there

mkdir -p sandbox/proxy/conf.d

mkdir -p sandbox/proxy/conf.stream.d


# pull and tag the sandbox and the proxy container

docker pull "$registry/$name:$version"

docker pull "$registry/$proxyName:$proxyVersion"



# start the docker container and proxy

if [ "$flavor" = "hdf" ]; then

hostname="sandbox-hdf.hortonworks.com"

elif [ "$flavor" = "hdp" ]; then

hostname="sandbox-hdp.hortonworks.com"

fi


version=$(docker images | grep $registry/$name | awk '{print $2}');


# Create cda docker network

docker network create cda 2>/dev/null


# Deploy the sandbox into the cda docker network

docker run --privileged --name $name -h $hostname --network=cda --network-alias=$hostname -d "$registry/$name:$version"


echo " Remove existing postgres run files. Please wait"

sleep 2

docker exec -t "$name" sh -c "rm -rf /var/run/postgresql/*; systemctl restart postgresql-9.6.service;"



#Deploy the proxy container.

sed 's/sandbox-hdp-security/sandbox-hdp/g' assets/generate-proxy-deploy-script.sh > assets/generate-proxy-deploy-script.sh.new

mv -f assets/generate-proxy-deploy-script.sh.new assets/generate-proxy-deploy-script.sh

chmod +x assets/generate-proxy-deploy-script.sh

assets/generate-proxy-deploy-script.sh 2>/dev/null


#check to see if it's windows

if uname | grep MINGW; then

sed -i -e 's/\( \/[a-z]\)/\U\1:/g' sandbox/proxy/proxy-deploy.sh

fi

chmod +x sandbox/proxy/proxy-deploy.sh 2>/dev/null

sandbox/proxy/proxy-deploy.sh