standard_init_linux.go:178: exec user process caused "exec format error"

standard_init_linux.go:178: exec user process caused permission denied
exec user process caused no such file or directory gunicorn
google standard_init_linux go 207
exec user process caused "exec format error" grafana
exec user process caused "exec format error" openvpn
dos2unix
starting container process caused no such file or directory

docker started throwing this error:

standard_init_linux.go:178: exec user process caused "exec format error"

whenever I run a specific docker container with CMD or ENTRYPOINT, with no regard to any changes to the file other then removing CMD or ENTRYPOINT. here is the docker file I have been working with which worked perfectly until about an hour ago:

FROM buildpack-deps:jessie

ENV PATH /usr/local/bin:$PATH

ENV LANG C.UTF-8

RUN apt-get update && apt-get install -y --no-install-recommends \
        tcl \
        tk \
    && rm -rf /var/lib/apt/lists/*

ENV GPG_KEY 0D96DF4D4110E5C43FBFB17F2D347EA6AA65421D
ENV PYTHON_VERSION 3.6.0

ENV PYTHON_PIP_VERSION 9.0.1

RUN set -ex \
    && buildDeps=' \
        tcl-dev \
        tk-dev \
    ' \
    && apt-get update && apt-get install -y $buildDeps --no-install-recommends && rm -rf /var/lib/apt/lists/* \
    \
    && wget -O python.tar.xz "https://www.python.org/ftp/python/${PYTHON_VERSION%%[a-z]*}/Python-$PYTHON_VERSION.tar.xz" \
    && wget -O python.tar.xz.asc "https://www.python.org/ftp/python/${PYTHON_VERSION%%[a-z]*}/Python-$PYTHON_VERSION.tar.xz.asc" \
    && export GNUPGHOME="$(mktemp -d)" \
    && gpg --keyserver ha.pool.sks-keyservers.net --recv-keys "$GPG_KEY" \
    && gpg --batch --verify python.tar.xz.asc python.tar.xz \
    && rm -r "$GNUPGHOME" python.tar.xz.asc \
    && mkdir -p /usr/src/python \
    && tar -xJC /usr/src/python --strip-components=1 -f python.tar.xz \
    && rm python.tar.xz \
    \
    && cd /usr/src/python \
    && ./configure \
        --enable-loadable-sqlite-extensions \
        --enable-shared \
    && make -j$(nproc) \
    && make install \
    && ldconfig \
    \
    && if [ ! -e /usr/local/bin/pip3 ]; then : \
        && wget -O /tmp/get-pip.py 'https://bootstrap.pypa.io/get-pip.py' \
        && python3 /tmp/get-pip.py "pip==$PYTHON_PIP_VERSION" \
        && rm /tmp/get-pip.py \
    ; fi \
    && pip3 install --no-cache-dir --upgrade --force-reinstall "pip==$PYTHON_PIP_VERSION" \
    && [ "$(pip list |tac|tac| awk -F '[ ()]+' '$1 == "pip" { print $2; exit }')" = "$PYTHON_PIP_VERSION" ] \
    \
    && find /usr/local -depth \
        \( \
            \( -type d -a -name test -o -name tests \) \
            -o \
            \( -type f -a -name '*.pyc' -o -name '*.pyo' \) \
        \) -exec rm -rf '{}' + \
    && apt-get purge -y --auto-remove $buildDeps \
    && rm -rf /usr/src/python ~/.cache

RUN cd /usr/local/bin \
    && { [ -e easy_install ] || ln -s easy_install-* easy_install; } \
    && ln -s idle3 idle \
    && ln -s pydoc3 pydoc \
    && ln -s python3 python \
    && ln -s python3-config python-config

RUN pip install uwsgi

RUN mkdir /config

RUN mkdir /logs

ENV HOME /var/www

WORKDIR /config

ADD conf/requirements.txt /config

RUN pip install -r /config/requirements.txt

ADD conf/wsgi.py /config

ADD conf/wsgi.ini /config

ADD conf/__init__.py /config

ADD start.sh /bin/start.sh

RUN chmod +x /bin/start.sh

EXPOSE 8000

ENTRYPOINT ["start.sh", "uwsgi", "--ini", "wsgi.ini"]

I forgot to put

#!/bin/bash

at the top of the sh file, problem solved.

Getting panic: spanic: standard_init_linux.go:178: exec user process , standard_init_linux.go:178: exec user process caused "no such file or directory" #​191. Closed. Dr-kyle opened this issue on Aug 20, 2018 · 3 comments. Closed  Seems to be realted to #24612 which is closed. Description After running the most recent Centos7 update, starting a container fails with "standard_init_linux.go:178: exec user process caused "permission denied".


Add this code

   #!/usr/bin/env bash

at the top of your scirpt file.

standard_init_linux.go:178: exec user process caused "exec format , panic: spanic: standard_init_linux.go:178: exec user process caused "no such file or directory"red] /usr/local/go/src/runtime/panic.go:481  standard_init_linux.go:178: exec user process caused "argument list too long" I found that the reason this occurs is because bash actually expands the asterisk to every matching file, producing a very long command line.


Another possible reason for this could be if the file is saved with Windows line endings (CRLF). Save it with Unix line endings (LF) and the file will be found.

Standard_init_linux.go:187: exec user process caused “no such file , I forgot to put #!/bin/bash. at the top of the sh file, problem solved. webserver_1 | standard_init_linux.go:178: exec user process caused "no such file or directory" Steps to reproduce the issue, if relevant: Do the same as described in the link:


I have faced same issue in RHEL 7.3, docker 17.05-ce when running offline loaded image. It appeared the default storage driver of RHEL/CentOS changed from device-mapper to overlay. Reverting back the driver to devicemapper fixed the problem.

dockerd --storage-driver=devicemapper

or

/etc/docker/daemon.json
{
  "storage-driver": "devicemapper"
}

docker image error: standard_init_linux.go:211: exec user process , standard_init_linux.go:178: exec user process caused "exec format error". Solution Verified - Updated January 29 2020 at 5:29 PM -. English. No translations  panic: standard_init_linux.go:178: exec user process caused “no such file or directory” [recovered] panic: standard_init_linux.go:178: exec user process caused “no such file or directory” Angular and Laravel Containers - /config/entry_point.sh Exit 1


Extending to the accepted answer:

For an alpine (without bash) image:

#!/bin/ash

at the top of the sh file, solves the problem.

Discussions, standard_init_linux.go:178: exec user process caused “no such file or directory”. It was working perfectly fine on our production environment,  Though I'm not familiar with go, I happen to find here since I met with the same problem (standard_init_linux.go:190: exec user process caused "exec format error"). I think it is because the system does not know how to execute the file.


Fix Docker Error: exec user process caused "no such file or directory", after install the following comes up in the logs ->. root@lpgaixmgmtlx01:/root/awx​>docker logs -f awx_task standard_init_linux.go:178: exec  standard_init_linux.go:211: exec user process caused "exec format error" Possible Fix. reason: Maybe it cant map the architecture. Steps to Reproduce and debugging done. e.g. your docker run command, pages to visit, CLI commands you ran $ docker-compose standard_init_linux.go:211: exec user process caused "exec format error" Debug steps I have


docker image error: standard_init_linux.go:211: exec user process caused “exec format error”. Summary. I run the command sudo docker run --detach \ --​hostname  Today I was working on migrating our node application from the titanic (about 600mb) ubuntu:14.04 image to the much more compact node:8-alpine image that is based on Linux Alpine, a Linux…


standard_init_linux.go:178: exec user process caused "exec format error" for docker running in GNS3 in Ubuntu. Unanswered. Answered. Hi, I am  standard_init_linux.go:178: exec user process caused "exec format error" Solution Verified - Updated 2020-01-29T17:29:29+00:00 - English