ogarcia / docker-taskd Goto Github PK

Just tried running on a pi4, and not unexpectedly, got:
standard_init_linux.go:211: exec user process caused "exec format error"

Tried to build it myself:

$ git clone https://github.com/ogarcia/docker-taskd.git
$ docker build -t taskwarrior .
Sending build context to Docker daemon  144.4kB
Step 1/9 : ARG ALPINE_VERSION
Step 2/9 : FROM alpine:${ALPINE_VERSION}
invalid reference format

Oh, I have to define alpine version, as I see in your docker file.

Maybe you can add a default to this? I just changed it to build on alpine:latest.

Hello folks!
I am trying to integrate this into your run.sh
https://github.com/bergercookie/taskwarrior-syncall

using ionotifyd https://wiki.alpinelinux.org/wiki/Inotifyd

would you merge such a change?
any hints or advice? especially regarding openrc use in docker?

Hey, this container looks really neat to set up taskd with the setup I am using.
I am using traefik for routing various things to different containers and have my own domain. It also regenerates the TLS certificates every few months. The Variables that are passed as well as the Documentation of the taskd say that I need to generate a frew things. I think I know how to the TLS certificates work, but seemingly taskd does something with a client certificate that I don’t quite understand. Would it be possible to help me integrate a procedure into the container, where it is possible to use the lets encrypt certificats.
Sorry for the not to technical comment, (I’m more the programmer, less the devops engineer)
Thanks so much already.

Hello!
First of all, thank you for your work. It's working perfectly, however, I had to manually generate the CA certificates as the CN is set to localhost completely ignoring either hostname or the CN environment variable set in my docker-compose.yml.

Subject: C=SE,ST=Västra Götaland,L=Göteborg,O=Göteborg Bit Factory,CN=localhost

This lead to the following error on the client:

Handshake failed.  Error in the certificate.

I may have a missed something. Otherwise, I would be really great if the generated certificate could have a configurable CN, using either the hostname or an environment variable.

EDIT: I'm aware of the vars file in the pki folder. However, there is no easy way to trigger the certificate generate from the container after editing this vars file. The two only way I can think of currently are:

• Running the generate script from the host (Which means installing the certtools)
• Executing it with docker exec

In the second case, I believe a quick change of the README.md to add something like:

In the case you want to change the parameters used for the certificate generation,
- Delete everything in /pki/ except the generate scripts and the vars file
- Edit the vars file
- Run docker exec -it <container-id> /var/taskd/pki/generate

could be beneficial and isn't redundant with the taskwarrior doc.

I can make a PR if you want.

Hello,
the documentation says something about the pid.file. Is this necessary to user in the container, too?

The command given in the documentaion:
$ taskd config --force pid.file $PWD/taskd.pid

Link to that docu:
https://taskwarrior.org/docs/taskserver/configure.html

Default value is pid.file=/tmp/taskd.pid. Is that okay for usage in docker?

For whatever reason, the generate script fails unless I specify that the others (ca, client, crl, and server) are located at /var/taskd/pki/. So I just appended /var/taskd/pki/ to each of the ./generate* lines and it worked, and knew where they were.

Then I ran into the same issue with the var file and did the same, appending . ./vars with /var/taskd/pki/ just before vars and it managed to find that as well.

I'm not sure why I'm getting this issue as there aren't any other issues submitted referring to it, but luckily the workaround is super simple.

Thank you for your great Dockerfile!

The configuration is straightforward, but I didnt found any hint how to generating the client certificate and where to put these files.

The following commands did the the job for me, but maybe there is an more easy way.

after RUNning the container, enter it with:
docker run -ti --rm -v /srv/taskd:/var/taskd myown/taskd /bin/sh

cd /var/taskd/pki
./generate.client timo 2>timo.out

cd ..
cd orgs
mkdir myown
cd myown
mkdir groups
mkdir users
chmod 700 users
cd users
mkdir timo
cd timo
echo "user=timo" >config
chmod 700 config

exit (leaving the container)

After that:
copy ca.cert.pem client.cert.pem client.key.pem to the client ( path ~/.task/ )

Ive added the following paragraph in the .taskrc
taskd.certificate=/root/.task/client.cert.pem
taskd.key=/root/.task/client.key.pem
taskd.ca=/root/.task/ca.cert.pem
taskd.server=localhost:53589
taskd.credentials=myown/timo/timo

Hi @ogarcia, I was wondering why your build doesn't make any changes to the vars file for cert generation. The docs mention that it must be changed; are you still able to run the server w/out this?