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

Instructions for managing M1 self-hosted runner #28086

Merged
merged 1 commit into from Sep 20, 2022

Conversation

holly-cummins
Copy link
Contributor

As discussed with @gsmet, I have documented the set up instructions for the Mac M1 self-hosted runner added in #27156.

I also removed some hardcoding from our podman instructions.

Copy link
Member

@gsmet gsmet left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Spotted a few micro things, otherwise it looks good. Thanks!

ACTIONS.md Outdated
### Non-root user

GitHub actions should not run with administrator privileges.
Make an account for the actions runner. *Grant administrator privileges to the account* (we will remove them later).
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Given you have a name for the account later, maybe add it there to be consistent?

ACTIONS.md Outdated Show resolved Hide resolved
ACTIONS.md Outdated
systemctl reboot
```

Now remove administrator privileges from the `githubactions` user.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe an hint of how it can be done? Or it's obvious for someone familiar with macOS?

ACTIONS.md Outdated Show resolved Hide resolved
ACTIONS.md Outdated Show resolved Hide resolved
ACTIONS.md Outdated Show resolved Hide resolved
Quarkus Documentation automation moved this from To do to Review pending Sep 20, 2022
Also added capitalisation corrections and improved instructions for user management.

Co-Authored-By: Guillaume Smet <guillaume.smet@gmail.com>
@holly-cummins
Copy link
Contributor Author

Suggestions implemented - thanks!

@gsmet
Copy link
Member

gsmet commented Sep 20, 2022

Could you squash the commits? Thanks.

@holly-cummins
Copy link
Contributor Author

holly-cummins commented Sep 20, 2022

The good news is that I actually had squashed the commits. The bad news is I hadn't pushed.

So I'm glad you didn't merge! There's a bit of extra commentary about managing users (per your suggestions) on top of what you saw when you last looked.

Quarkus Documentation automation moved this from Review pending to Reviewer approved Sep 20, 2022
@gsmet gsmet added the triage/waiting-for-ci Ready to merge when CI successfully finishes label Sep 20, 2022
@gsmet gsmet merged commit 06c146e into quarkusio:main Sep 20, 2022
Quarkus Documentation automation moved this from Reviewer approved to Done Sep 20, 2022
@quarkus-bot quarkus-bot bot added this to the 2.14 - main milestone Sep 20, 2022
@quarkus-bot quarkus-bot bot removed the triage/waiting-for-ci Ready to merge when CI successfully finishes label Sep 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

None yet

2 participants