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

Pulumi/Pulumi does not use Pulumi/Base #114

Open
RobbieMcKinstry opened this issue Sep 30, 2022 · 0 comments
Open

Pulumi/Pulumi does not use Pulumi/Base #114

RobbieMcKinstry opened this issue Sep 30, 2022 · 0 comments
Labels
impact/performance Something is slower than expected kind/bug Some behavior is incorrect or out of spec

Comments

@RobbieMcKinstry
Copy link
Contributor

What happened?

The pulumi/pulumi image uses python as a base image.

Ideally, we'd like pulumi/pulumi (a.k.a. the kitchen sink image) to share layers with the base image, so that caching the base image speeds up downloading the kitchen sink image. This is useful in contexts where one cluster is deploying both the kitchen sink image and the base image.

Steps to reproduce

Inspect the shared layers between pulumi/pulumi and pulumi/base and see that no layers are shared.

Expected Behavior

Expected the kitchen sink docker image to start with (on line 16):

FROM pulumi/pulumi-base:${PULUMI_VERSION}

Actual Behavior

It actually starts with FROM debian:11-slim

Output of pulumi about

No response

Additional context

No response

Contributing

Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

@RobbieMcKinstry RobbieMcKinstry added impact/performance Something is slower than expected kind/bug Some behavior is incorrect or out of spec labels Sep 30, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
impact/performance Something is slower than expected kind/bug Some behavior is incorrect or out of spec
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant