Docker Compose fails build on Win 10 and macOS

Question

Docker Compose fails build on Win 10 and macOS

daddydrac opened this issue 3 years ago · comments

docker-compose build base-notebook
Building base-notebook
#1 [internal] load git source github.com/jupyter/docker-stacks.git#master:base-notebook

#1 ERROR: subdir not supported yet
------
 > [internal] load git source github.com/jupyter/docker-stacks.git#master:base-notebook:
------
failed to solve with frontend dockerfile.v0: failed to read dockerfile: failed to load cache key: subdir not supported yet
Service 'base-notebook' failed to build : Build failed

Jacob Tomlinson · Answer 1 · Mon Jun 14 2021 17:21:26 GMT+0800 (China Standard Time)

Could you please share your Docker version? Typically we support docker-ce on Linux and we use Ubuntu in CI.

It seems that specifying git subdirectories is not supported in all Docker build modes (buildkit).

docker/for-linux#1102

walter211 · Answer 2 · Wed Jun 16 2021 13:23:36 GMT+0800 (China Standard Time)

I met the same Docker version 20.10.6, build 370c289

walter211 · Answer 3 · Wed Jun 16 2021 13:43:43 GMT+0800 (China Standard Time)

Could you please share your Docker version? Typically we support docker-ce on Linux and we use Ubuntu in CI.

It seems that specifying git subdirectories is not supported in all Docker build modes (buildkit).

docker/for-linux#1102

how to solve this temporarily?

walter211 · Answer 4 · Wed Jun 16 2021 14:02:17 GMT+0800 (China Standard Time)

I clone the jupyter repo manually but is this build cost is normal？

walter211 · Answer 5 · Wed Jun 16 2021 14:02:35 GMT+0800 (China Standard Time)

MacOS Bigsur

Jacob Tomlinson · Answer 6 · Wed Jun 16 2021 17:11:09 GMT+0800 (China Standard Time)

There is an existing problem with building these images using buildkit. I am wondering if buildkit became the default in Windows/macOS lately?

I am curious why you are building the images. We build these for you and publish them to DockerHub. Are you just trying to start a Dask cluster with docker? Or are you specifically trying to build the images yourself?

Code Vampire · Answer 7 · Wed Jun 16 2021 19:14:59 GMT+0800 (China Standard Time)

I was just trying to run the docker compose file like how you’re supposed to. I did pull the image first, but then the docker compose files still build it on its own without looking in local docker registry apparently in windows. Protip: I never use buildkit for my stuff and would advise to stop using it. It creates far too many deployment problems. I normally use helm but I have some local work that needs to be done.

…

On Wed, Jun 16, 2021 at 4:11 AM Jacob Tomlinson ***@***.***> wrote: There is an existing problem with building these images using buildkit. I am wondering if buildkit became the default in Windows/macOS lately? I am curious why you are building the images. We build these for you and publish them to DockerHub. Are you just trying to start a Dask cluster with docker? Or are you specifically trying to build the images yourself? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#156 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABHVQHHJXMJ3RH6NZ3SHCNTTTBTEDANCNFSM46RF4NSQ> .

Jacob Tomlinson · Answer 8 · Wed Jun 16 2021 23:00:00 GMT+0800 (China Standard Time)

I wonder if the confusion here is the intent of the docker compose file.

This repo is just for building images. The docker compose file is set up for building them every time.

I wonder if we need to shuffle things round a bit here and have two files, one for building and one for using.

Jacob Tomlinson · Answer 9 · Tue Aug 17 2021 18:25:27 GMT+0800 (China Standard Time)

#171 separated the build stack from the example stack which should solve this issue.