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
...my understanding is that if I have already run make docker and then I run make all, then this if statement will get run again but since the image now exists, the docker build command should not get run.
However, it looks to me like the docker build command does in fact get run regardless of the output of docker image inspect.
Are you able to fix this?
The text was updated successfully, but these errors were encountered:
@tghosth yes, I believe the appropriate solution is to put the image on a repository and only pull in the action, instead of building in the action at all.
We could potentially have an action that built and pushed the image if the docker dir changes.
#1680 removes the docker target from any of the other targets, so this issue should be resolved now. You can still build the docker image using make docker.
Hi @ike,
I was experimenting with running
make docker
and thenmake all
separately.My understanding is that
make docker
will just create the docker image and load it into the local docker image.Looking at the following code...
...my understanding is that if I have already run
make docker
and then I runmake all
, then this if statement will get run again but since the image now exists, thedocker build
command should not get run.However, it looks to me like the
docker build
command does in fact get run regardless of the output ofdocker image inspect
.Are you able to fix this?
The text was updated successfully, but these errors were encountered: