rebuild image --no-cache

[Razvan0925]

Is your feature request related to a problem? Please describe.
I have to rebuild an image as a repository is updated. The problem is that if I build it again, it is built from cache, it does not download the repository again. Right now the only solution is to detele the service, the container and the image, build the image again and update the stack. What I would like is a --no-cache toggle button in the Build image page.

Describe the solution you'd like
A toggle button for --no-cache build command option.

Describe alternatives you've considered
An extra parameters field for build command.

[maxtrem]

Any news on this? This is a quite annoying problem.
As a workaround I'm adding random ls statements into the dockerfile. This works somehow but is annoying and just lets the cache grow.
Is there some better way to tackle this problem?

[kasprzakdanielt]

Any news on this?

[alex-bul]

[JadenSWang]

bump

[alvarogabrielgomez]

news?

[AsharDweedar]

.

[dreamid27]

ok

[doptime]

it's badlly needed. I need it to make devops become easy

[doptime]

an alternative way:
ARG random_chars_to_disable_cache_axasdes=1
https://stackoverflow.com/questions/35134713/disable-cache-for-specific-run-commands

[Opulis1]

an alternative way: ARG random_chars_to_disable_cache_axasdes=1 https://stackoverflow.com/questions/35134713/disable-cache-for-specific-run-commands

The problem with this method is you can not pass ARGs in portainer either as its currently not a supported feature, so once the ARG is set, if it never changes its still cached.

Honestly it is a little concerning that no one from the dev team has even bothered to jump in with their thoughts in over 4 years. Not even a simple "hey guys, thanks for the request. Unfortunately our plate is pretty full but we will try to get it on the road map in the future" or some sort of explanation as to why its not feasible. The ability to pass ARGs and the ability to disable image caching are pretty fundamental components of docker, and without them portainer really loses potential in the enterprise market. Yes ill run it in my homelab because it works fine for really simple tasks, but I know that I can never buy the enterprise license and use it for my clients like this.

[nathanielastudillo]

Mega-bump, having an option to rebuild without the cache would really help my CI/CD flow.

[drewbitt]

Rebuilding on updates was dealt with last year for Docker Compose (#6288) but getting regular Docker to rebuild was skipped. You can get this to work in Compose but not the plain Docker build UI... funny. Anyway, since this has been moved to a Discussion (despite their docs on Feature Requests), none of the reactions in the issue matter anymore - not that it got this implemented before. I encourage anyone who still cares though to upvote the feature request in the Discussion list then.

[mayberryjp]

i do "WORKDIR /myapp-v1.0.x" and keep incrementing the x every image. seems to avoid a cache

[mayberryjp]

noting you can't have two docker images with the same workdir or else one will still cache

[Nick-Portainer]

Thanks for raising this - I have raised this internally for discussion.

internal: PCT-328

[Nick-Portainer]

Hey all, update from us -
We understand the value of this and are looking at how we can add this as part of future improvements to the Image build feature. Thank you for your comments around this, I will update you as this progresses.

Have a fantastic day and thank you for the support 🎉

[mayberryjp]

in the meantime - an easy work around is just update the workdir

[Wamy-Dev]

desperately needed

[tg-ats]

Been another year, any news?

[mayberryjp]

im not the dev but just change the workdir and add a version number in it and it stops caching

[tg-ats]

Change from the default workdir? And the version number would be for each rebuild or just once?

[mayberryjp]

i do one for every rebuild

[KlaasT]

Any news on this? This really gives issues with gitops on our project.

[mayberryjp]

I suggested a proper work around like 5 times. Why are people still waiting around? You simply just change the workdir for every build. Its such an easy fix i dont understand why people are still blocked

[AlecBlance]

One way to solve this is to use pull_policy: build in your docker compose as stated here #6288