docs icon indicating copy to clipboard operation
docs copied to clipboard

Add a note about docker installed from snap

Open dsame opened this issue 3 years ago • 2 comments

Why:

One of user had a problem with the docker in self-hosted environment. The investigation showed it used the engine installed with snap and that was a reason of the problem.

Original issue: https://github.com/actions/setup-java/issues/348

What's being changed (if available, include any code snippets, screenshots, or gifs):

I added a sectionDocker engine setup

Check off the following:

  • [ x] I have reviewed my changes in staging (look for the "Automatically generated comment" and click the links in the "Preview" column to view your latest changes).
  • [x] For content changes, I have completed the self-review checklist.

dsame avatar Jul 26 '22 12:07 dsame

Automatically generated comment ℹ️

This comment is automatically generated and will be overwritten every time changes are committed to this branch.

The table contains an overview of files in the content directory that have been changed in this pull request. It's provided to make it easy to review your changes on the staging site. Please note that changes to the data directory will not show up in this table.


Content directory changes

You may find it useful to copy this table into the pull request summary. There you can edit it to share links to important articles or changes and to give a high-level overview of how the changes in your pull request support the overall goals of the pull request.

Source Preview Production What Changed
actions/using-github-hosted-runners/about-github-hosted-runners.md fpt
ghec
ghes@ 3.6 3.5 3.4 3.3 3.2
fpt
ghec
ghes@ 3.6 3.5 3.4 3.3 3.2

fpt: Free, Pro, Team ghec: GitHub Enterprise Cloud ghes: GitHub Enterprise Server ghae: GitHub AE

github-actions[bot] avatar Jul 26 '22 12:07 github-actions[bot]

@dsame Thanks so much for opening a PR! I'll get this triaged for review :zap:

cmwilson21 avatar Jul 27 '22 15:07 cmwilson21

Addressing this in an internal PR, so that it can be moved to the self-hosted runner troubleshooting section.

martin389 avatar Sep 13 '22 02:09 martin389

These changes have now shipped in a separate PR. The content will be live here in a few minutes: https://docs.github.com/en/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-which-docker-engine-is-installed-on-the-runner

Thanks for the PR, @dsame 👍

martin389 avatar Sep 13 '22 06:09 martin389