Closed janusn closed 11 months ago
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.
You should not need to use the universal cron mod on this container. cron is included and running by default. I will look into adjusting the mod to skip running cron if the container already runs it.
You should not need to use the universal cron mod on this container. cron is included and running by default. I will look into adjusting the mod to skip running cron if the container already runs it.
Thanks for looking into it.
Actually, I have encountered this issue when I modified the host file of /docker/nextcloud/config/crontabs/abc and the volumes maps "/docker/nextcloud/config:/config:rw" inside the container. I did not change any cron settings otherwise.
I just looked a little closer and see that we don't have an out of the box way to run cron as abc without the mod or having the root cron use s6-setuidgid abc
.
This is a bit more motivation for making adjustments to the cron mod. I'll have to think through exactly how to handle it though.
Is there an existing issue for this?
Current Behavior
A task declared in /config/crontabs/abc is called twice.
Expected Behavior
A line in /config/crontabs/abc should be called once.
Steps To Reproduce
Suppose the container is named as 'nextcloud' and created by docker compose with
./config
mapped to/config
inside the container.$ sudo docker exec -it nextcloud /bin/bash
# echo '* * * * * /bin/echo `whoami` >> /config/debug-crond.log ; /bin/echo `date` >> /config/debug-crond.log' >> /config/crontabs/abc
# exit
$ sudo docker compose restart
$ cat ./config/debug-crond.log
Environment
CPU architecture
x86-64
Docker creation
Container logs