- cannot create directory: No such file or directory #2218
- Comments
- nagisa commented Jun 14, 2017
- sunjoong commented Jun 14, 2017
- CherryDT commented Jun 17, 2017
- nagisa commented Jun 17, 2017 •
- jaron-l commented Mar 26, 2019
- deploy:release — mkdir: cannot create directory ‘****/releases/1’: No such file or directory #1818
- Comments
- jjpeleato commented Mar 6, 2019
- Description
- Steps to reproduce
- Content of deploy.php
- Output log
- Windows Docker Error — standard_init_linux.go:211: exec user process caused «no such file or directory» #9
- Comments
- joaotnlima commented Jan 17, 2020
- riggraz commented Jan 17, 2020
- joaotnlima commented Jan 17, 2020 •
- riggraz commented Jan 17, 2020
- joaotnlima commented Jan 17, 2020 •
- riggraz commented Jan 19, 2020
- riggraz commented Jan 25, 2020
- versedpro commented Jun 5, 2020 •
- PhilippWuerfel commented Jun 10, 2020 •
- vr6tdi commented Jul 9, 2020
- diegosurita commented Jul 11, 2020
- Kyle-Williamson-Dev commented Jul 18, 2020
- matthias-ijewski commented Sep 24, 2020
- chroot: can’t execute ‘/bin/su’: No such file or directory #516
- Comments
- rickglyn commented May 25, 2016
cannot create directory: No such file or directory #2218
Comments
nagisa commented Jun 14, 2017
|
No idea. Sorry. I haven’t access to the machine (anymore).
- What you’re doing and what’s happening: (Copy&paste specific commands and their output, or include screen shots)
All I know that it was something along the lines of:
The only way to create directory again I’ve found is restarting; nothing else I’ve tried helped.
- What’s wrong / what should be happening instead:
The error message is nonsensical; Should just create the directory.
- Strace of the failing command, if applicable: (If is failing, then run strace -o strace.txt -ff , and post the strace.txt output here)
Sorry. I haven’t access to the machine (anymore). I will try reproducing elsewhere and report if I can hit it again.
The text was updated successfully, but these errors were encountered:
sunjoong commented Jun 14, 2017
@nagisa — It sounds similar to this scenario but. I’m not sure;
CherryDT commented Jun 17, 2017
@sunjoong Not sure, because in your case the error makes sense because your current directory doesn’t exist anymore so you are trying to create a directory inside a nonexistent one, while in the OPs description he did do cd .. before creating the directory.
nagisa commented Jun 17, 2017 •
I could not re-reproduce it. I will reopen if I ever hit this again.
jaron-l commented Mar 26, 2019
For documentation purposes, I was able to reproduce but it wasn’t a WSL error. It’s a permission issue. For me, it’s because I had Windows 10’s ransomware protection on which refuses write access to certain protected folders and refused WSL. Disabling it for mkdir specifically fixed the issue.
«
#Initial error
user@computer:/mnt/c/Users/directory/WSL$ mkdir test
mkdir: cannot create directory ‘test’: No such file or directory
#showing that my current directory exists
user@computer:/mnt/c/Users/directory/WSL$ pwd
/mnt/c/Users/directory/WSL
#change to directory not protected by windows 10 ransomware protection (inside WSL home folder)
user@computer:/mnt/c/Users/directory/WSL$ cd /home/user
#mkdir now works
user@computer: $ mkdir new
user@computer: $ ls
new
#turned off ransomware protection for WSL and mkdir now works
user@computer:/mnt/c/Users/directory/WSL$ mkdir test
user@computer:/mnt/c/Users/directory/WSL$ ls
test
«
Источник
deploy:release — mkdir: cannot create directory ‘****/releases/1’: No such file or directory #1818
Comments
jjpeleato commented Mar 6, 2019
DescriptionHello! I have a problem when I run the deployment process to production environment. In the «deploy:release» it returns the failed command: The ssh user has all the privileges (the user is not root), it is an ssh connection of my server for one project. I think there is a problem for non-root users. If I run the same recipe with the root user, everything works correctly, but I need to run with the specific project user The following command is executed successfully: Should «deploy_path» be deleted? Manually execute the two commands with the user not «root» from the folder where I connect and the deployer command does not work. Steps to reproduceNothing, only run dep deploy pro Content of deploy.phpOutput logThe text was updated successfully, but these errors were encountered: Источник Windows Docker Error — standard_init_linux.go:211: exec user process caused «no such file or directory» #9Commentsjoaotnlima commented Jan 17, 2020This 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. PG:Bad connection. Works in Windows now 😉 The text was updated successfully, but these errors were encountered: riggraz commented Jan 17, 2020Hey joaotnlima, thanks for posting! standard_init_linux.go:211 is a well known issue for Windows users.
Yes, EOL are a problem in Windows. I think you wanted to say to change them from LF to CRLF.
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 •
I believe you need to change them to LF — at least i did that.
Yes correct. I believe there is a better way, but i just wanted it working right away riggraz commented Jan 17, 2020I 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?
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
riggraz commented Jan 19, 2020Thanks for the information. In these day I’ve been pretty busy, I’ll try it out in a few days. riggraz commented Jan 25, 2020Unfortunately 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 •
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? PhilippWuerfel commented Jun 10, 2020 •
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 vr6tdi commented Jul 9, 2020
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 Same here, CRLF to LF helped to fix diegosurita commented Jul 11, 2020
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 Same here, thanks! Kyle-Williamson-Dev commented Jul 18, 2020
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. PG:Bad connection. 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, 2020You 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. Источник chroot: can’t execute ‘/bin/su’: No such file or directory #516Commentsrickglyn commented May 25, 2016Hi 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 The text was updated successfully, but these errors were encountered: Источник |
