Open pabsan-0 opened 1 year ago
Same issue, however DOCKER_BUILDKIT=0
is working perfectly for the time being, thank you so much.
I'll attach logs in case it helps.
$ ./run.sh --model 7b --with-cuda
[+] Building 14.6s (0/1)
[+] Building 14.8s (0/1)
=> [internal] booting buildkit 14.8s
[+] Building 14.8s (1/1) FINISHED
=> ERROR [internal] booting buildkit 14.8s
=> => starting container buildx_buildkit_default 14.8s
------
> [internal] booting buildkit:
------
> [internal] booting buildkit:
#0 14.81 time="2023-11-09T00:33:26Z" level=warning msg="using host network as the defaultime="2023-11-09T00:33:26Z" level=warning msg="using host network as the default"
#0 14.81 time="2023-11-09T00:33:26Z" level=warning msg="skipping containerd worker, as \"/run/containerd/containerd.sock\" does not exist"
#0 14.81 dtime="2023-11-09T00:33:26Z" level=info msg="found 1 workers, default=\"ubuhemwsxd9lgh279m7pd1wac\""
#0 14.81 time="2023-11-09T00:33:26Z" level=warning msg="using host network as the defaultime="2023-11-09T00:33:26Z" level=warning msg="using host network as the default"
#0 14.81 time="2023-11-09T00:33:26Z" level=warning msg="skipping containerd worker, as \"/run/containerd/containerd.sock\" does not exist"
#0 14.81 dtime="2023-11-09T00:33:26Z" level=info msg="found 1 workers, default=\"ubuhemwsxd9lgh279m7pd1wac\""
#0 14.81 `time="2023-11-09T00:33:26Z" level=warning msg="currently, only the default worker can be used."
#0 14.81 \time="2023-11-09T00:33:26Z" level=info msg="running server on /run/buildkit/buildkitd.sock"
#0 14.81 time="2023-11-09T00:33:26Z" level=warning msg="skipping containerd worker, as \"/run/containerd/containerd.sock\" does not exist"
#0 14.81 time="2023-11-09T00:33:26Z" level=warning msg="currently, only the default worker can be used."
#0 14.81 time="2023-11-09T00:33:26Z" level=warning msg="currently, only the default worker can be used."
#0 14.81
------
#0 14.81 `time="2023-11-09T00:33:26Z" level=warning msg="currently, only the default worker can be used."
#0 14.81 \time="2023-11-09T00:33:26Z" level=info msg="running server on /run/buildkit/buildkitd.sock"
#0 14.81 time="2023-11-09T00:33:26Z" level=warning msg="skipping containerd worker, as \"/run/containerd/containerd.sock\" does not exist"
#0 14.81 time="2023-11-09T00:33:26Z" level=warning msg="currently, only the default worker can be used."
#0 14.81 time="2023-11-09T00:33:26Z" level=warning msg="currently, only the default worker can be used."
#0 14.81
------
http: invalid Host header
Same problem with WSL ubuntu on Win11 :
root@ASUSRFZ13:/home/containers/llama-gpt# ./run.sh --model 7b
[+] Building 17.0s (1/1) FINISHED
=> ERROR [internal] booting buildkit 17.0s
=> => pulling image moby/buildkit:buildx-stable-1 1.8s
=> => creating container buildx_buildkit_default 15.3s
------
> [internal] booting buildkit:
#0 17.03 time="2023-11-16T21:04:47Z" level=warning msg="using host network as the defaultime="2023-11-16T21:04:47Z" level=warning msg="using host network as the default"
#0 17.03 time="2023-11-16T21:04:47Z" level=warning msg="skipping containerd worker, as \"/run/containerd/containerd.sock\" does not exist"
#0 17.03 dtime="2023-11-16T21:04:47Z" level=info msg="found 1 workers, default=\"w5oo16t8h2xbxo8abznff0azn\""
#0 17.03 `time="2023-11-16T21:04:47Z" level=warning msg="currently, only the default worker can be used."
#0 17.03 \time="2023-11-16T21:04:47Z" level=info msg="running server on /run/buildkit/buildkitd.sock"
#0 17.03 time="2023-11-16T21:04:47Z" level=warning msg="skipping containerd worker, as \"/run/containerd/containerd.sock\" does not exist"
#0 17.03 time="2023-11-16T21:04:47Z" level=warning msg="currently, only the default worker can be used."
#0 17.03 time="2023-11-16T21:04:47Z" level=warning msg="currently, only the default worker can be used."
#0 17.03
------
http: invalid Host header
root@ASUSRFZ13:/home/containers/llama-gpt#
Hi, I'm on ubuntu 22.04 LTS. I tried the launch script on bash and I got the following:
This appears to be a
docker compose
issue. You can override it temporarily by prependingDOCKER_BUILDKIT=0
to your launch command. See more in this stack overflow question.