Hi, I just read in the blogpost about the recipe and was very happy, because I just newly discovered tailscale and love the clients.
So I am new to everything and a bit confused.
I already understood, that the webui is found on mydomain.xyz/web and that it's only a mere frontend, but I don't get how to "access" the container and using headscale, creating API keys and so on, because there neither seems to be bash nor sh installed
abra app run mydomain.xyz app sh
OCI runtime exec failed: exec failed: unable to start container process: exec: "sh": executable file not found in $PATH
FATA
any hints on this? could make a "getting started" doc from it
Hi, I just read in the blogpost about the recipe and was very happy, because I just newly discovered tailscale and love the clients.
So I am new to everything and a bit confused.
I already understood, that the webui is found on `mydomain.xyz/web` and that it's only a mere frontend, but I don't get how to "access" the container and using headscale, creating API keys and so on, because there neither seems to be `bash` nor `sh` installed
```
abra app run mydomain.xyz app sh
OCI runtime exec failed: exec failed: unable to start container process: exec: "sh": executable file not found in $PATH
FATA
```
any hints on this? could make a "getting started" doc from it
I'm getting started on this but I just pushed changes to add oidc support which allowed clients to use authentik to login
Next on my list is to figure out how to add clients manually for machines (non-human users) and manage access to machines based on client attributes like groups
To run the command line do this:
abra app run mydomain.xyz app -- headscale help
Note this:
The headscale/headscale Docker container is based on a "distroless" image that does not contain a shell or any other debug tools. If you need to debug your application running in the Docker container, you can use the -debug variant, for example headscale/headscale:x.x.x-debug.
I'm getting started on this but I just pushed changes to add oidc support which allowed clients to use authentik to login
Next on my list is to figure out how to add clients manually for machines (non-human users) and manage access to machines based on client attributes like groups
To run the command line do this:
```bash
abra app run mydomain.xyz app -- headscale help
```
Note this:
> The headscale/headscale Docker container is based on a "distroless" image that does not contain a shell or any other debug tools. If you need to debug your application running in the Docker container, you can use the -debug variant, for example headscale/headscale:x.x.x-debug.
https://headscale.net/0.24.1/setup/install/container/#debugging-headscale-running-in-docker
ah perfect, thanks a lot. that's exactly the info I was missing. Didn't know about distroless images :)
so I will start a "Getting started" section in the docs with these two info and perhaps add as I continue exploring.
ah perfect, thanks a lot. that's exactly the info I was missing. Didn't know about distroless images :)
so I will start a "Getting started" section in the docs with these two info and perhaps add as I continue exploring.
I'm getting started on this but I just pushed changes to add oidc support which allowed clients to use authentik to login
Next on my list is to figure out how to add clients manually for machines (non-human users) and manage access to machines based on client attributes like groups
To run the command line do this:
abra app run mydomain.xyz app -- headscale help
Note this:
The headscale/headscale Docker container is based on a "distroless" image that does not contain a shell or any other debug tools. If you need to debug your application running in the Docker container, you can use the -debug variant, for example headscale/headscale:x.x.x-debug.
another short note on the oidc-support. It was quite confusing not being able to set an oidc-client, just figured out it's hardcoded as headscale in the conf. So before releasing we might add this?
> I'm getting started on this but I just pushed changes to add oidc support which allowed clients to use authentik to login
>
> Next on my list is to figure out how to add clients manually for machines (non-human users) and manage access to machines based on client attributes like groups
>
> To run the command line do this:
>
> ```bash
> abra app run mydomain.xyz app -- headscale help
> ```
>
> Note this:
>
> > The headscale/headscale Docker container is based on a "distroless" image that does not contain a shell or any other debug tools. If you need to debug your application running in the Docker container, you can use the -debug variant, for example headscale/headscale:x.x.x-debug.
>
> https://headscale.net/0.24.1/setup/install/container/#debugging-headscale-running-in-docker
another short note on the oidc-support. It was quite confusing not being able to set an oidc-client, just figured out it's hardcoded as `headscale` in the conf. So before releasing we might add this?
I'm getting started on this but I just pushed changes to add oidc support which allowed clients to use authentik to login
Next on my list is to figure out how to add clients manually for machines (non-human users) and manage access to machines based on client attributes like groups
To run the command line do this:
abra app run mydomain.xyz app -- headscale help
Note this:
The headscale/headscale Docker container is based on a "distroless" image that does not contain a shell or any other debug tools. If you need to debug your application running in the Docker container, you can use the -debug variant, for example headscale/headscale:x.x.x-debug.
another short note on the oidc-support. It was quite confusing not being able to set an oidc-client, just figured out it's hardcoded as headscale in the conf. So before releasing we might add this?
Yeah, we can also change it from hardcoded to an env variable!
> > I'm getting started on this but I just pushed changes to add oidc support which allowed clients to use authentik to login
> >
> > Next on my list is to figure out how to add clients manually for machines (non-human users) and manage access to machines based on client attributes like groups
> >
> > To run the command line do this:
> >
> > ```bash
> > abra app run mydomain.xyz app -- headscale help
> > ```
> >
> > Note this:
> >
> > > The headscale/headscale Docker container is based on a "distroless" image that does not contain a shell or any other debug tools. If you need to debug your application running in the Docker container, you can use the -debug variant, for example headscale/headscale:x.x.x-debug.
> >
> > https://headscale.net/0.24.1/setup/install/container/#debugging-headscale-running-in-docker
>
> another short note on the oidc-support. It was quite confusing not being able to set an oidc-client, just figured out it's hardcoded as `headscale` in the conf. So before releasing we might add this?
Yeah, we can also change it from hardcoded to an env variable!
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Hi, I just read in the blogpost about the recipe and was very happy, because I just newly discovered tailscale and love the clients.
So I am new to everything and a bit confused.
I already understood, that the webui is found on
mydomain.xyz/weband that it's only a mere frontend, but I don't get how to "access" the container and using headscale, creating API keys and so on, because there neither seems to bebashnorshinstalledany hints on this? could make a "getting started" doc from it
I'm getting started on this but I just pushed changes to add oidc support which allowed clients to use authentik to login
Next on my list is to figure out how to add clients manually for machines (non-human users) and manage access to machines based on client attributes like groups
To run the command line do this:
Note this:
https://headscale.net/0.24.1/setup/install/container/#debugging-headscale-running-in-docker
ah perfect, thanks a lot. that's exactly the info I was missing. Didn't know about distroless images :)
so I will start a "Getting started" section in the docs with these two info and perhaps add as I continue exploring.
another short note on the oidc-support. It was quite confusing not being able to set an oidc-client, just figured out it's hardcoded as
headscalein the conf. So before releasing we might add this?Yeah, we can also change it from hardcoded to an env variable!