-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
docker compose --profile auto up --build fails with OSError #433
Comments
this is the first time I have seen this kind of error. Doing a quick google search tells me that the path might be incorrect or too long for the operating system, but I don't think that is the case here. on windows maybe but on linux it is like 4KB for the file path. Let's try and debug this:
|
Hello, me with the same error... I use ProxMox, and LXC with docker |
This issue is stale because it has been open 14 days with no activity. Remove stale label or comment or this will be closed in 7 days. |
This issue was closed because it has been stalled for 7 days with no activity. |
Anyone figure out a solution for this problem? stable-diffusion-webui-docker used to work for me, but somewhere along the way I started getting the error reported here. Rocky 8.7 -comfy container builds without issue |
I will re-open this and try to investigate the issue |
been throwing spaghetti at the wall to no avail... I didn't trust docker compose build --no-cache, so I tried cleaning build cache bits up... docker builder prune -a. no change I've gone through the services/AUTOMATIC1111/Dockerfile and commented out the mount cache lines and disabled buildkit. no luck I thought maybe upgrading pip prior to installing the AUTO1111 requirement might help....
Trips over the same Errno 22 Invalid argument while uninstalling pip. hmmmm |
This issue is stale because it has been open 14 days with no activity. Remove stale label or comment or this will be closed in 7 days. |
downgrading docker a few versions, didn't help When I get a chance I'll try to blow everything docker away and start fresh. The only thing slightly out of the ordinary is the docker root directory is not /var/lib/docker/. I don't see why that would cause a problem, but who knows. |
This issue is stale because it has been open 14 days with no activity. Remove stale label or comment or this will be closed in 7 days. |
Are you running on zfs by any chance? What is your I ran into the same problem and root-caused it to docker using the My fix was to use the The strange thing is I have two installs of Ubuntu on the same physical machine, both using ZFS, both with docker installed, but one of them defaults to using the |
winner winner chicken dinner! thanks @shrimp6089 I enabled zfs storage driver, cleared build cache, build container, no errors! |
thank you @shrimp6089 , I will add this to the FAQ in case other users face the same problem. |
Hello, i have same issue
docker-compose version:
pip version:
you suggestions are welcome, thankyou! |
System info:
Arch linux, up to date packages:
No problem running these commands (exit code 0 with last command)
Issue is here:
Any suggestions welcome!
The text was updated successfully, but these errors were encountered: