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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, this is what we've been working through with:
The namespace has to be
ghcr.io/tailscale/codespace
for GitHub to list it. They rejectedghcr.io/tailscale/codespace/tailscale
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Right,
ghcr.io/tailscale/codespace
is the namespace butghcr.io/tailscale/codespace/tailscale
is required to make it work in the features list. It's the same at https://github.com/devcontainers/devcontainers.github.io/pull/119/files#diff-213a25c23998b235e92e81da59bbf14a591fa6332ee3d14a662ad4471e621bcbR230There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yep, as written in the README doesn't work, but with this change the codespace can be created successfully!
In the docs (https://tailscale.com/kb/1160/github-codespaces/) explain that you should set up your codespace as
– this README and those docs should agree!