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.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Running the compose.yml file only results in this error:
Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: "--model": executable file not found in $PATH: unknown
I have used the .env file with no success, and I'm not sure the compose.yml file even knows to reference it; there's no mention of it anywhere. Manually adding it via environment: -.env or env_file: .env does nothing to remedy the error. I've manually specified the model and model directory in the compose.yml, yet I get the same error. This is only from using the given compose.yml.
Wow, got it fixed... I'll leave this up as this wasn't very clear for me.
On the prebuilt page for DockerHub, it says "Experimental tag (and likely all future tags) requires now launching python3 koboldcpp.py, so my command block now looks like so". My understanding of this was that the new command block had yet to be implemented and was exclusive to the "experimental" tag. Apparently the latest image requires this new command block. I feel like that should be worded differently...
Anywho, if you're having the same issue as I was, try this one:
F1zzyD
changed the title
"Error Response from Daemon" when using Docker Compose
DockerHub Command Block Listed as "Experimental", But Latest Version Uses It
Nov 17, 2024
Running the compose.yml file only results in this error:
I have used the .env file with no success, and I'm not sure the compose.yml file even knows to reference it; there's no mention of it anywhere. Manually adding it via
environment: -.env
orenv_file: .env
does nothing to remedy the error. I've manually specified the model and model directory in the compose.yml, yet I get the same error. This is only from using the given compose.yml.Here is my compose.yml:
The text was updated successfully, but these errors were encountered: