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

Allow rebuild container without cache #2200

Closed
rubensa opened this issue Jan 27, 2020 · 6 comments
Closed

Allow rebuild container without cache #2200

rubensa opened this issue Jan 27, 2020 · 6 comments
Assignees
Labels
containers Issue in vscode-remote containers plan-item A plan item
Milestone

Comments

@rubensa
Copy link

rubensa commented Jan 27, 2020

Sometimes I have a Dockerfile that installs software downloaded form Internet. If download fails (cause a network failure or something), the image is build anyway.

The problem is that I can't force VSCode to rebuild the image (so, once the network issue is fixed, the software can be downloaded and installed) using Remote-Containers: Rebuild Container as it always uses cache.

Please provide a Remote-Containers: Rebuild Container without Cache, or similar command, containing the --no-cache option.

@chrmarti chrmarti added containers Issue in vscode-remote containers feature-request Request for new features or functionality labels Jan 27, 2020
@AlexisLessard
Copy link

I too would like this feature. I sometimes have issues in nodejs where an issue with docker itselfs requires me to rebuild the entire image. But I can't. My only workaround is to change the source image from node:12 to node:11 and vice-versa. This should be either an option in .devcontainer.json or an entirely new command.

@JohnBetaCode
Copy link

do an echo "something" run command when you want to rebuild, ugly, but useful

@Alaric84
Copy link

yes I think especially for devcontainers where we want always with the latest version the --no-chache option should be possible. I would be happy with a buildArgs in the devcontainer.json
Better to have the no-chache everytime (and pay this with some seconds startup time) than to have outdated stuff in the development environment.

@ghost
Copy link

ghost commented Dec 3, 2020

Work around: copy the docker build command from the log, append --no-cache and run in a separate terminal, return to vscode and "Re-open in Container" to use the refreshed cache
(helpfully, the paths in the command appear to use absolute paths, so you can just copy-paste)

@ThomasTosik
Copy link

Is there any plan for this? After some time and issues i stumbled upon this issue and its frustrating that i can not truly rebuild/clean (with --no-cache). Manualy deleting an image only works sometimes but when you are working in a bigger context; this leads often to "delete all images because i dont now comfortably what layer is used by cache".

@aniongithub
Copy link

Maintainers, this sort of thing would be trivial if this extension was open-sourced, you'd get a PR in no time flat. Please consider open sourcing this extension!

@chrmarti chrmarti self-assigned this Jul 8, 2021
@chrmarti chrmarti added this to the July 2021 milestone Jul 8, 2021
@chrmarti chrmarti added plan-item A plan item and removed feature-request Request for new features or functionality labels Jul 20, 2021
@github-actions github-actions bot locked and limited conversation to collaborators Sep 3, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
containers Issue in vscode-remote containers plan-item A plan item
Projects
None yet
Development

No branches or pull requests

7 participants