Skip to content

pulumi versions build up over time consuming disk space #976

Open

Description

What happened?

I am looking at my github runner disk and seeing that the /actions-runner/_work/_tool/pulumi directory is consuming 17GB

[root@ip-XX-XX-X-XXX _tool]# du -h --max-depth=1 .
475M    ./node
17G     ./pulumi
418M    ./go
48M     ./buildx
18G     .

When I investigate I see the following

[root@ip-XX-XXX-X-XXX pulumi]# du -h --max-depth=1 .
136M    ./3.22.1
136M    ./3.24.1
136M    ./3.25.1
137M    ./3.26.1
137M    ./3.27.0
139M    ./3.28.0
138M    ./3.29.1
138M    ./3.30.0
175M    ./3.32.1
180M    ./3.33.1
179M    ./3.33.2
186M    ./3.34.0
185M    ./3.34.1
185M    ./3.35.0
185M    ./3.35.1
185M    ./3.35.2
185M    ./3.35.3
186M    ./3.36.0
186M    ./3.37.0
186M    ./3.37.1
186M    ./3.37.2
192M    ./3.38.0
198M    ./3.39.0
198M    ./3.39.1
200M    ./3.40.0-alpha.1662150830
198M    ./3.39.2
198M    ./3.39.3
199M    ./3.40.0
203M    ./3.40.2
210M    ./3.41.1
210M    ./3.42.0
210M    ./3.43.1
210M    ./3.44.2
211M    ./3.44.3
211M    ./3.45.0
211M    ./3.46.0
211M    ./3.46.1
216M    ./3.47.0
216M    ./3.47.1
216M    ./3.47.2
216M    ./3.48.0
218M    ./3.49.0
220M    ./3.50.0
220M    ./3.50.1
220M    ./3.50.2
220M    ./3.51.0
221M    ./3.51.1
221M    ./3.52.0
221M    ./3.52.1
221M    ./3.53.0
221M    ./3.53.1
220M    ./3.54.0
220M    ./3.55.0
220M    ./3.56.0
220M    ./3.57.1
224M    ./3.58.0
224M    ./3.59.0
224M    ./3.59.1
224M    ./3.60.0
224M    ./3.60.1
224M    ./3.61.0
226M    ./3.61.1
226M    ./3.62.0
226M    ./3.63.0
226M    ./3.64.0
226M    ./3.65.0
226M    ./3.65.1
226M    ./3.66.0
267M    ./3.67.0
267M    ./3.67.1
266M    ./3.68.0
306M    ./3.69.0
302M    ./3.70.0
302M    ./3.71.0
299M    ./3.72.0
302M    ./3.72.1
302M    ./3.72.2
302M    ./3.73.0
302M    ./3.74.0
17G     .
[root@ip-10-100-5-234 pulumi]#

Expected Behavior

Pulumi action should cleanup after itself rather than put work on me to clean it up.

Steps to reproduce

Normal use of Pulumi Action

Output of pulumi about

...

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).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

No one assigned

    Labels

    kind/bugSome behavior is incorrect or out of specSome behavior is incorrect or out of spec

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions