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
If you put a Dockerfile.dazel at the root of your workspace, you can build from the workspace root and everything works nicely. If, however, you cd into a subdirectory and invoke dazel build, dazel will try to pull the default dazel/dazel image instead of using the Dockerfile.dazel.
This appears to be because the workspace path is not joined to the dockerfile variable (source).
It can be worked around by adding the following to .dazelrc at the workspace root:
dazel also appears to create a .dazel_run file in the subdirectory in this case, but this just results in an unnecessary file and and a one-time unnecessary container restart.
The text was updated successfully, but these errors were encountered:
If you put a
Dockerfile.dazel
at the root of your workspace, you can build from the workspace root and everything works nicely. If, however, youcd
into a subdirectory and invokedazel build
, dazel will try to pull the defaultdazel/dazel
image instead of using theDockerfile.dazel
.This appears to be because the workspace path is not joined to the
dockerfile
variable (source).It can be worked around by adding the following to
.dazelrc
at the workspace root:But this is obviously fragile.
dazel also appears to create a
.dazel_run
file in the subdirectory in this case, but this just results in an unnecessary file and and a one-time unnecessary container restart.The text was updated successfully, but these errors were encountered: