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
I am using this action to build an image with a lot of dependencies in it for the application I am developing. These several dependencies take a long time to build and install onto the docker image, and therefore the docker image takes a long time to build.
When I am developing the docker image locally, the docker cache stores the intermediate layers so that it only needs to rebuild the layers after and including any changes I made. I am wondering if this action has a similar feature. Does it pull down the image from dockerhub to see which layer to start from?
Thank you
The text was updated successfully, but these errors were encountered:
Version 2 has been merged to the main branch and is therefore available via uses: docker/build-push-action@v2 (mutable tag).
As a reminder, this new version changes drastically and works with 3 new actions (login, setup-buildx and setup-qemu) that we have created. Many usage examples have been added to handle most use cases.
And it should fix this current issue. Don't hesitate if you have any questions.
I am using this action to build an image with a lot of dependencies in it for the application I am developing. These several dependencies take a long time to build and install onto the docker image, and therefore the docker image takes a long time to build.
When I am developing the docker image locally, the docker cache stores the intermediate layers so that it only needs to rebuild the layers after and including any changes I made. I am wondering if this action has a similar feature. Does it pull down the image from dockerhub to see which layer to start from?
Thank you
The text was updated successfully, but these errors were encountered: