Do not build guides in containers so container build works #2366
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.

For a while, the container version of our getting started instructions hasn't been working. This is not ideal, and it's particularly unfortunate now that installing Ruby on MacOS laptops is hard (the install is breaking with ssl compatibility issues, and the fix requires an older version of Ruby to be present).
Serving via container works for simpler sites, and the problem isn't our Gemfile. I've narrowed the problem down to something pulled in via the
_guidesdirectory, perhaps the_generated-docdirectory. While I continue to debug, I've got a tactical fix. This has the benefit of speeding up container serving a lot, by just not serving the guides.