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

Remove all tools #222

Closed
RomainFallet opened this issue Jan 3, 2020 · 4 comments
Closed

Remove all tools #222

RomainFallet opened this issue Jan 3, 2020 · 4 comments
Assignees
Labels
enhancement New feature or request question Further information is requested

Comments

@RomainFallet
Copy link

RomainFallet commented Jan 3, 2020

Tool information

  • Tool name: None
  • Add or update? Remove
  • Desired version: None
  • Approximate size: 0 Kb

Area for Triage:

Question, Bug, or Feature?: Question

Virtual environments affected

  • [*] macOS 10.15
  • [*] Ubuntu 16.04 LTS
  • [*] Ubuntu 18.04 LTS
  • [*] Windows Server 2016 R2
  • [*] Windows Server 2019

Hello,

I would like to have fresh virtual machines instead of preinstalled ones in order to test installation scripts with Github Actions.

Is it possible to have an uninstall/cleanup script that does the exact opposite of all pre-installation things which I could run before my tests?

Thanks!

@github-actions github-actions bot added Area: Git bug Something isn't working enhancement New feature or request question Further information is requested labels Jan 3, 2020
@oldskool
Copy link

oldskool commented Jan 3, 2020

Sounds like you want a clean Docker container and do your things in there.

So get a Dockerfile like (all code below is untested/from the top of my head, but just for illustation):

FROM ubuntu:18.04

COPY your-install-script.sh /

ENTRYPOINT /your-install-script.sh

And then just build and run that from the runner:

- name: Build empty container
  run: docker build -t my-installer-test .

- name: Run it
  run: docker run --rm my-installer-test

Should allow you to do just what you want in an empty environment.

@RomainFallet
Copy link
Author

RomainFallet commented Jan 3, 2020 via email

@kaylangan kaylangan removed Area: Git bug Something isn't working labels Jan 3, 2020
@alepauly
Copy link
Contributor

alepauly commented Jan 8, 2020

@RomainFallet we don't support that and there aren't any plans for something like that at this time. You can always self-host your runner. I know it's not as simple as the hosted runners but since you don't need anything preinstalled, it should be fairly straightforward to set up.

@alepauly alepauly closed this as completed Jan 8, 2020
@samuela
Copy link

samuela commented Nov 3, 2023

This is also a pain point simply because of how heavyweight the runners are. I frequently find myself debugging jobs that failed due disk space issues. There are even folks building sorta workarounds for this: https://github.com/easimon/maximize-build-space.

Is there any way we could just get a "minimal" runner? Something with only the bare essentials?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request question Further information is requested
Projects
None yet
Development

No branches or pull requests

5 participants