Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(clean) run a prune command to clear the build cache #241

Merged
merged 1 commit into from
Feb 1, 2022
Merged

Conversation

Tieske
Copy link
Member

@Tieske Tieske commented Dec 20, 2021

If not pruning the build cache, the next run will simply rebuild
the images from the cache without actually rebuilding. In case of
a pongo clean or pongo nuke that's not what we want.

See #188 #94 #189

If not pruning the build cache, the next run will simply rebuild
the images from the cache without actually rebuilding. In case of
a `pongo clean` or `pongo nuke` that's not what we want.
Tieske added a commit to Kong/kong that referenced this pull request Dec 20, 2021
This fixes the deeper underlying problem related to Kong/kong-pongo#241 .

In those cases the `make dev` overall failed because LuaRocks failed, but it was not signaled. Hence docker assumes the image to be valid and even caches the results of the docker commands. Despite them being faulty.
Tieske added a commit to Kong/kong that referenced this pull request Dec 20, 2021
This fixes the deeper underlying problem related to Kong/kong-pongo#241 .

In those cases the `make dev` overall failed because LuaRocks failed, but it was not signaled. Hence docker assumes the image to be valid and even caches the results of the docker commands. Despite them being faulty.
@Tieske Tieske merged commit c6bd7f3 into master Feb 1, 2022
@Tieske Tieske deleted the prune branch February 1, 2022 08:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant