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
Describe the issue
Since this commit was added (jupyter/docker-stacks@5365b9f) building with latest commit fails with the following error:
[+] Building 0.0s (1/1) FINISHED docker:default
=> [gpu-jupyter internal] load build definition from Dockerfile 0.0s
=> => transferring dockerfile: 20.19kB 0.0s
=> WARN: InvalidDefaultArgInFrom: Default value for ARG $ROOT_IMAGE results in empty or invalid base image name (line 31) 0.0s
=> WARN: InvalidDefaultArgInFrom: Default value for ARG $BASE_IMAGE results in empty or invalid base image name (line 189) 0.0s
=> WARN: InvalidDefaultArgInFrom: Default value for ARG $BASE_IMAGE results in empty or invalid base image name (line 274) 0.0s
=> WARN: InvalidDefaultArgInFrom: Default value for ARG $BASE_IMAGE results in empty or invalid base image name (line 329) 0.0s
=> WARN: UndefinedArgInFrom: FROM argument 'ROOT_IMAGE' is not declared (line 31) 0.0s
failed to solve: base name ($ROOT_IMAGE) should not be blank
To Reproduce
./generate-Dockerfile.sh --python-only --commit latest
docker compose up --build -d
Expected Behavior
It should build without errors.
Additional Context
Just happens when you use a commit equal or newer than 5365b9f79fa4ffbb20f10133cc6ac5bec5046302
The text was updated successfully, but these errors were encountered:
This is definitely a good point! The single issue that still occurs with it is, that the env variables BASE_CONTAINER and BASE_IMAGE must be set dynamically. Otherwise, the commit selection would not work for commits older than August which deprecates all versions based on Ubuntu 22 or earlier.
GPU-Jupyter Issue Report
Issue Description
Describe the issue
Since this commit was added (jupyter/docker-stacks@5365b9f) building with latest commit fails with the following error:
To Reproduce
Expected Behavior
It should build without errors.
Additional Context
Just happens when you use a commit equal or newer than 5365b9f79fa4ffbb20f10133cc6ac5bec5046302
The text was updated successfully, but these errors were encountered: