Linux exec no such file or directory

Windows Docker Error — standard_init_linux.go:211: exec user process caused «no such file or directory» #9

Comments

joaotnlima commented Jan 17, 2020

This happens in windows environments.

To advance the topic you should edit all .sh files in the repo and change the EOL from CRLF to LF. This fixes the issue.
Then another bug appeared btw:

PG:Bad connection.
Added db to windows hosts and added port 5432 to the docker-file in ports for db.

Works in Windows now 😉

The text was updated successfully, but these errors were encountered:

riggraz commented Jan 17, 2020

Hey joaotnlima, thanks for posting!

standard_init_linux.go:211 is a well known issue for Windows users.

you should edit all .sh files in the repo and change the EOL from CRLF to LF

Yes, EOL are a problem in Windows. I think you wanted to say to change them from LF to CRLF.

Added db to windows hosts and added port 5432 to the docker-file in ports for db

Could you elaborate more on this, please? For the windows hosts you mean the host file c:\windows\system32\drivers\etc\hosts ?

joaotnlima commented Jan 17, 2020 •

Yes, EOL are a problem in Windows. I think you wanted to say to change them from LF to CRLF.

I believe you need to change them to LF — at least i did that.

Could you elaborate more on this, please? For the windows hosts you mean the host file

Yes correct. I believe there is a better way, but i just wanted it working right away

riggraz commented Jan 17, 2020

I tried your solution but it doesn’t work on my machine. I’m on Windows 10 Home and I’m using Docker Toolbox (because Docker Desktop is not compatible with Windows 10 Home). What OS and Docker are you using?

I believe you need to change them to LF — at least i did that.

Can you please check whether all files are in LF or just the ones you manually changed?

joaotnlima commented Jan 17, 2020 •

All files (.sh) are LF including Dockerfile and docker-compose.yml.

I’m using windows 10 Pro Version 10.0.18362 Build 18362
Docker Desktop 2.1.0.5 (40693)

riggraz commented Jan 19, 2020

Thanks for the information. In these day I’ve been pretty busy, I’ll try it out in a few days.

riggraz commented Jan 25, 2020

Unfortunately I was not able to make it work on my machine.

If you want, you can open a pull request with the changes to make it work under Windows. Then we’ll ask for other windows users to test it and, when it works, merge it.

versedpro commented Jun 5, 2020 •

Could you elaborate more on this, please? For the windows hosts you mean the host file

Yes correct. I believe there is a better way, but i just wanted it working right away

Would you mind to explain more about hosts of windows?
I faced a problem creating db.

PhilippWuerfel commented Jun 10, 2020 •

you should edit all .sh files in the repo and change the EOL from CRLF to LF

Yes, EOL are a problem in Windows. I think you wanted to say to change them from LF to CRLF.

Had the same issue on Docker
I changed my shell script on Windows 10 from CRLF to LF and that worked for me!

vr6tdi commented Jul 9, 2020

you should edit all .sh files in the repo and change the EOL from CRLF to LF

Yes, EOL are a problem in Windows. I think you wanted to say to change them from LF to CRLF.

Had the same issue on Docker
I changed my shell script on Windows 10 from CRLF to LF and that worked for me!

Same here, CRLF to LF helped to fix

diegosurita commented Jul 11, 2020

you should edit all .sh files in the repo and change the EOL from CRLF to LF

Yes, EOL are a problem in Windows. I think you wanted to say to change them from LF to CRLF.

Had the same issue on Docker
I changed my shell script on Windows 10 from CRLF to LF and that worked for me!

Same here, thanks!

Kyle-Williamson-Dev commented Jul 18, 2020

This happens in windows environments.

To advance the topic you should edit all .sh files in the repo and change the EOL from CRLF to LF. This fixes the issue.
Then another bug appeared btw:

PG:Bad connection.
Added db to windows hosts and added port 5432 to the docker-file in ports for db.

Works in Windows now 😉

I would like to know how you did this. I’m very new and this is my first time building a docker app. No idea what files I need to change or how. You say edit all .sh files. I only have one, my entrypoint.sh that the Rails Docker-Compose quickstart guide shows how to build the Dockerfile and stuff. I’ve built my rails app image, which is my portfolio I’m going to build, and got the server to start and everything on my laptop. But when I come to my desktop to pull the image down and docker-compose up, I’m getting this error we’re talking about in this thread. So what part of the file am I changing? am I REPLACING .sh? or adding the LF after it?

matthias-ijewski commented Sep 24, 2020

You can use this code in your dockerfile to fix line breaks:

RUN sed -i -e ‘s/\r$//’ /entrypoint.sh

Replace /entrypoint.sh with the path to the file with the suspected wrong line breaks.

You can’t perform that action at this time.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.

Источник

standard_init_linux.go:178: exec user process caused «no such file or directory» #215

Comments

GingerMoon commented Mar 31, 2017

Which lab is it that you’re having issues with?
In-container Java Development: IntelliJ Community Edition
https://github.com/docker/labs/blob/master/developer-tools/java-debugging/IntelliJ-README.md

Description

I got the error below after running the command: docker-compose up
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:
https://github.com/docker/labs/blob/master/developer-tools/java-debugging/IntelliJ-README.md
But is blocked at:
Running the application
Open a terminal and go to the application directory. Start the application with docker-compose

Describe the results you received:
webserver_1 | standard_init_linux.go:178: exec user process caused «no such file or directory»

Additional information you deem important (e.g. issue happens only occasionally):

Output of docker version :

Docker version 17.03.1-ce, build c6d412e
Windows10 Enterprise

The text was updated successfully, but these errors were encountered:

Источник

Standard_init_linux.go:187: exec user process caused “no such file or directory”

Alpine + Docker + Bash

TL:DR bash doesn’t exist in Linux Alpine, you either use sh or install it.

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 distribution that is tiny and barebones, really barebones.

After setting everything up, cleaning the Dockerfile and setting up a node_modules dependencies cache. I build the image, and it was time to run it.

After deploying it to EC2, It was not booting and I kept receiving this error.

It was working perfectly fine on our production environment, and I was sure that was an error introduced by my change.

It didn’t say which file was missing, but I did know alpine doesn’t have a lot of commands you would usually expect in most Linux distros.

So I ran an Alpine locally on my dev machine and ran every single command on my entryscript. Every single command was working.

So it began, I started googling the issue, and after many pages suggesting me to run dos2unix without success. I ran into this.

So it looks like alpine is so barebones it doesn’t even have bash installed by default. It only has sh and the first line of my script was #!/bin/bash and docker tried to run my script with that shell. Because it wasn’t found, it was throwing that really useless error. I lost a few hours of life on this.

The solution is quite easy, either change #!/bin/bash to !#/bin/sh or install bash with apk add —update bash . And that is it.

Источник

Debian: No such file or directory — а файл есть

Здравствуйте, уважаемые. Скачал btsync (у меня arm, по ссылке Linux ARM тут), положил в /usr/bin и не могу запустить:

Как так и что с этим делать?

P.S. Тоже самое происходит, если переместить исполняемый файл, например, в домашний каталог.

P.S.S. Debian Jessie, вот такая железка.

chmod +x точно не поможет?

apparmor, selinux, noexec?

noexec на разделе

такое бывает когда исполняемый файл например предназначенный для 32 битной архитектуры пытаются запустить в 64-битной системе

А что покажет file btsync ? Необязательно на самой железке.

apparmor, selinux, chattr — это что? Что посмотреть?

В общем, похоже-таки несовместимость архитектур. Придётся пересобирать из исходников. Источник: http://otvety.google.ru/otvety/thread?tid=1e74bf1617bdb4b6

Try to run the following command

I had the same issue on Cubieboard.

Try to run the following command:

sudo ln -s /lib/arm-linux-gnueabihf/ld-linux.so.3 /lib/ld-linux.so.3

На Debian 7.6.0 (Linux 3.2.0-4-amd64 #1 SMP Debian 3.2.60-1+deb7u3 x86_64 GNU/Linux) столкнулся с той же проблемой. Для запуска 32-битного приложения может потребоваться пакет ia32-libs-i386. Дебиан по умолчанию не дает его установить из-за зависимостей. Решается таким образом:

sudo dpkg —add-architecture i386 sudo apt-get update sudo apt-get install ia32-libs-i386 (тянет за собой 60Мб зависимостей)

Источник

chroot: can’t execute ‘/bin/su’: No such file or directory #516

Comments

rickglyn commented May 25, 2016

Hi all Linux deploy fans,

I’ve had the app running fine with jessie and ssh on 5.1.1 but now updated to 6.0.1 on Note 4 SM-N910F. I’ve reinstalled LD, Busybox, rooted SU ok and selinux permissive but I’ve got this / these problems still. Just trying to get ssh working.

Would appreciate it if any of you guys could point to what’s going wrong.

[13:04:56] + container_configure dns mtab
[13:04:56] + [ 2 -eq 0 ]
[13:04:56] + container_mounted
[13:04:56] + is_mounted /data/data/ru.meefik.linuxdeploy/linux
[13:04:56] + local mount_point=/data/data/ru.meefik.linuxdeploy/linux
[13:04:56] + [ -n /data/data/ru.meefik.linuxdeploy/linux ]
[13:04:56] + grep -q /data/data/ru.meefik.linuxdeploy/linux /proc/mounts
[13:04:56] Configuring the container:
[13:04:56] dns . +
[13:04:56] + return 0
[13:04:56] + [ 0 -ne 0 ]
[13:04:56] + msg Configuring the container:
[13:04:56] + echo Configuring the container:
[13:04:56] + local item
[13:04:56] + configure_part dns
[13:04:56] + msg -n dns .
[13:04:56] + echo -n dns .
[13:04:56] + set -e
[13:04:56] + [ -z ]
[13:04:56] + getprop net.dns1
[13:04:56] + local dns1=208.67.222.222
[13:04:56] + getprop net.dns2
[13:04:56] + local dns2=208.67.220.220
[13:04:56] + local dns_list=208.67.222.222 208.67.220.220
[13:04:56] + [ -z 208.67.222.222 -a -z 208.67.220.220 ]
[13:04:56] + printf
[13:04:56] + local dns
[13:04:56] + echo nameserver 208.67.222.222
[13:04:56] + echo nameserver 208.67.220.220
[13:04:56] + exit 0
[13:04:56] + [ 0 -eq 0done
[13:04:56] mtab . ]
[13:04:56] + msg done
[13:04:56] + echo done
[13:04:56] + return 0
[13:04:56] + configure_part mtab
[13:04:56] + msg -n mtab .
[13:04:56] + echo -n mtab .
[13:04:56] + set -e
[13:04:56] + rm -f /data/data/ru.meefik.linuxdeploy/linux/etc/mtab
[13:04:56] + grep /data/data/ru.meefik.linuxdeploy/linux+ sed s|/data/data/ru.meefik.linuxdeploy/linux/*|/|g
[13:04:56] /proc/mounts
[13:04:56] + exit 0
[13:04:56] done
[13:04:56] Starting services:
[13:04:56] SSH [:22] . + [ 0 -eq 0 ]
[13:04:56] + msg done
[13:04:56] + echo done
[13:04:56] + return 0
[13:04:56] + return 0
[13:04:56] + msg Starting services:
[13:04:56] + echo Starting services:
[13:04:56] + local item
[13:04:56] + container_start ssh
[13:04:56] + [ 1 -eq 0 ]
[13:04:56] + msg -n SSH [:22] .
[13:04:56] + echo -n SSH [:22] .
[13:04:56] + ssh_started
[13:04:56] + local item pidfile pid
[13:04:56] + pidfile=/data/data/ru.meefik.linuxdeploy/linux/var/run/sshd.pid
[13:04:56] + [ -e /data/data/ru.meefik.linuxdeploy/linux/var/run/sshd.pid ]
[13:04:56] + [ -n -a -e /proc/ ]
[13:04:56] + pidfile=/data/data/ru.meefik.linuxdeploy/linux/run/sshd.pid
[13:04:56] + [ -e /data/data/ru.meefik.linuxdeploy/linux/run/sshd.pid ]
[13:04:56] + [ -n -a -e /proc/ ]
[13:04:56] + return 1
[13:04:56] + [ -e /data/data/ru.meefik.linuxdeploy/linux/var/run -a ! -e /data/data/ru.meefik.linuxdeploy/linux/var/run/sshd ]
[13:04:56] + [ -e /data/data/ru.meefik.linuxdeploy/linux/run -a ! -e /data/data/ru.meefik.linuxdeploy/linux/run/sshd ]
[13:04:56] + grep key
[13:04:56] + ls /data/data/ru.meefik.linuxdeploy/linux/etc/ssh/
[13:04:56] ls: /data/data/ru.meefik.linuxdeploy/linux/etc/ssh/: No such file or directory
[13:04:56] + [ -z ]
[13:04:56] + chroot_exec -u root ssh-keygen -A
[13:04:56] + unset TMP TEMP TMPDIR LD_PRELOAD LD_DEBUG
[13:04:56] + [ -u = -u ]
[13:04:56] + local username=root
[13:04:56] + shift 2
[13:04:56] + [ 1 -gt 0 ]
[13:04:56] + chroot /data/data/ru.meefik.linuxdeploy/linux /bin/su — root -c ssh-keygen -A
[13:04:56] chroot: can’t execute ‘/bin/su’: No such file or directory
[13:04:56] + local sshd= which sshd
[13:04:56] + chroot_exec -u root which sshd -p 22
[13:04:56] + unset TMP TEMP TMPDIR LD_PRELOAD LD_DEBUG
[13:04:56] + [ -u = -u ]
[13:04:56] + local username=root
[13:04:56] + shift 2
[13:04:56] + [ 1 -gt 0 ]
[13:04:56] + chroot /data/data/ru.meefik.linuxdeploy/linux /bin/su — root -c which sshd -p 22
[13:04:56] fail
[13:04:56] chroot: can’t execute ‘/bin/su’: No such file or directory
[13:04:56] + [ 127 -eq 0 ]
[13:04:56] + msg fail
[13:04:56] + echo fail
[13:04:56] + return 0
[13:04:56] + [ 0 -eq 0 ]
[13:04:56] + [ -z ssh ]
[13:04:56] + return 0
[13:04:56] + printf $’

The text was updated successfully, but these errors were encountered:

Источник