codespace
codespace copied to clipboard
tailscale
Experimenting with codespaces
**MUAT TURUN APLIKASI TERMUX** Pastikan anda muat turun aplikasi TERMUX dari sumber yang betul. • Muat turun aplikasi _F-Droid_ Muat turun : [https://f-droid.org/F-Droid.apk]() • Muat turun dan Pasang _TERMUX_ dari...
After the codespace is built including the feature (which now is available, thank you), I try the following: ```bash tailscale up --accept-routes failed to connect to local tailscaled; it doesn't...
After running `tailscale up` with an `--exit-node` the connection to the Codespace goes away and I'm unable to connect to the Codespace again. Also tried with more options: ```shell sudo...
Seems like tailscaled is unable to update the dns resolver settings. Tailscaled log: ``` logtail started Program starting: v1.34.1-t328b49c4d-g921b59a2e, Go 1.19.2-ts3fd24dee31: []string{"tailscaled", "--state=mem:"} LogID: xxxxx logpolicy: using system state directory...
Installation of the devcontainer feature failed because my baseimage had no /usr/local/sbin dir. It is based on alpine. https://github.com/SimonHaas/webspace/blob/ae8f32217c349a0aaefc0dd8cc36d728f186bc2b/.devcontainer/Dockerfile#L5
This devcontainer feature stores the Tailscale state in `/workspaces/.tailscale/` but that is outside the structure that is automatically mapped by VSCode to the local project directory so the state was...
# Description The tailscale devcontainer feature only supports x86_64 machines due to the hardcoded `tailscale_url`. This PR addresses this issue by dynamically assigning the `tailscale_url` depending on the platform #...
This may have been originally written for Codespaces, but Codespaces are basically just fancy devcontainers and this works just fine in a regular devcontainer like in VSCode. If you list...
While this plug-in does work on my M1 MacBook I noticed that is was being executed by Rosetta inside the ARM64 container as this extract from `ps` demonstrates: `/run/rosetta/rosetta /usr/local/sbin/tailscaled`...
Can add logs would make it easier to identify the issue. Would it be possible to add more debugging information in the logs to facilitate troubleshooting? missing keys devcontainer logs...
