-
Notifications
You must be signed in to change notification settings - Fork 999
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue #21 is back: Execution bit lost on /docker/mount.sh #36
Comments
@hughk can you update the command from |
I have updated the executable status again, I have to find a permanent solution for this problem... |
So I stashed my stuff and git pulled again. I chmoded the copy of mount.sh both in hlkm and in the AUTOMATIC1111 sub-directories checked the execute bit was on, It was and tried again. Same problem. I'm unsure though exactly what is happening as we now have two Dockerfiles. So Im not quite sure which is causing the problem. |
@AbdBarho Complete delete of local depository (except for models) and GIT pull seems to work |
@hughk glad it was fixed, since it is the second you had this problem, maybe it is a problem with git config, can you run this for the future?
Info from the git docs: core.fileMode Some filesystems lose the executable bit when a file that is marked as executable is checked out, or checks out a non-executable file with executable bit on. git-clone(1) or git-init(1) probe the filesystem to see if it handles the executable bit correctly and this variable is automatically set as necessary. |
Building the container works. Starting the container fails (again) with the following message:
stable-diffusion-webui-docker-model-1 | + /docker/mount.sh
stable-diffusion-webui-docker-model-1 | /bin/bash: line 1: /docker/mount.sh: Permission denied
Steps to Reproduce
Hardware / Software:
Additional context
Attempted to add a chmod +x /docker/mount.sh before the command is run in dockerfile, the command does execute but does not improve things. Docker seems to work otherwise. A different version seems to have been deployed.
The text was updated successfully, but these errors were encountered: