Skip to content

Conversation

@lurtz
Copy link
Contributor

@lurtz lurtz commented Feb 11, 2026

For CI container images shall be small so that CI is fast. However for developers we usually want more tools to increase productivity.

TODO

  • use image in developer devcontainer
  • remove duplicated code

@lurtz lurtz force-pushed the minimized-buildcontainer branch 2 times, most recently from 2ddd82c to a663cd8 Compare February 12, 2026 13:28
For CI container images shall be small so that CI is fast. However for developers we usually want more tools to increase productivity.
@lurtz lurtz force-pushed the minimized-buildcontainer branch from a663cd8 to 6f760f3 Compare February 12, 2026 13:36
@lurtz lurtz force-pushed the minimized-buildcontainer branch from 6f760f3 to 6214610 Compare February 12, 2026 16:13
@lurtz
Copy link
Contributor Author

lurtz commented Feb 12, 2026

As as I build using a builder created with docker buildx create, the devcontainer build cannot find the already build buildcontainer image, which was done one step before. Using the default builder it works.

Therefore I put this on hold, because I think it might not be worth the effort. At the moment the v1.1.0 version of the container needs 37s to come up in CI. Its size is 4.3GB. Total build time was 6 minutes and the build time of the communication repo is 12 minutes.

Further information information I found about this issue:

Here I doubt that I can pass the proper buildx options down via devcontainercli.

If we ever want to have a dedicated image for CI, maybe it is easier to store the devcontainer features in a separate repository and use those. It is not possible to reuse local features.

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.

1 participant