Paolo Asperti

If you want to use docker (or k8s) secrets, please refer to [this section](https://github.com/rustdesk/rustdesk-server#use-docker-secrets-to-store-the-key-pair) of the readme.

> Surely they should be read from the original path only? The two paths have different attack surfaces, so this behaviour is circumventing the docker secrets mechanism. I agree with...

just to frame this a little more, you can start hbbs like this: ```sh hbbs -k IRvYWCnv72zAFBYO4LT9h5yUfqLQXG0/DVw68yFfr55UrtLfm6TjcOcvo+nLtscsA4VxvKcVJfJYC2rpi2R2DA== ``` You don't even need a key file. But this approach has a...

MIPS is not ready for production use, not enough performances for relaying even a small number of connections.

Can you please explain what you're trying to achieve?

Thanks. Can you please create a new release? This will trigger the creation of new container images in docker hub, fixing currently unusable images.

I already tried, and I tried again. I can confirm that the dagu binary is amd64 while the base image (alpine) is aarch64. `latest` tag, pushed 21 days ago: [see...

```sh # pull image docker pull yohamta/dagu:latest # create temporary container docker create --name dagu yohamta/dagu:latest # create temporary directory mkdir ~/delme ; cd ~/delme # export the container filesystem...

same: ```sh 12:15:45 me@mypc:~/ee$ cat etc/apk/arch aarch64 12:15:49 me@mypc:~/ee$ file usr/local/bin/dagu usr/local/bin/dagu: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), statically linked, Go BuildID=Zd3PfvCj3nrg7LF2HBdD/nTozrA-wclTAQf49Jx9f/2SQrrDehmM4LtGQA8S2l/iM59oNhz5SqDcB9XyBW1, with debug_info, not stripped ```

same problem as before... with this image ```sh docker images REPOSITORY TAG IMAGE ID CREATED SIZE ghcr.io/dagu-dev/dagu latest 9cd3319a80a8 5 hours ago 47.2MB ```