GithubHelp home page GithubHelp logo

vdirsyncer-dockerized's People

Contributors

bleala avatar

Stargazers

avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar

Watchers

avatar avatar avatar

Forkers

sblop feralith milesteg1 c0d3m0nky

vdirsyncer-dockerized's Issues

warning: Failed to discover collections for google

I'm new here. I'm trying to get help. I'm not sure, if the Issues-Section is the right place.
So please forgive me, in case it is not. I will remove it.

I'm running Vdirsyncer-Dockerized on a Synology-Nas in Docker.
I'm tying to sync the local cal with my google-calendar.
I installed pip install vdirsyncer[google]
Authentication with Google Caldav works fine, but I keep on getting the following warning:
warning: Failed to discover collections for google

Config:

General

[general]
status_path = "/vdirsyncer/status/"

Pairs

[pair google_local]
a = "google"
b = "local"
collections = ["from a", "from b"]
conflict_resolution = "b wins"

[storage google]
type = "google_calendar"
token_file = "/vdirsyncer/google_token"
client_id = "78214-f1bcquf5q1c6n66i7lb.apps.googleusercontent.com"
client_secret = "GO************************UqBT"

[storage local]
type = "caldav"
url = "https://a*****b.c******d.ch/caldav/tobias.faust/hjqbrkvn/"
username = "username"
password = "password"

Logfile

date stream content
2022-07-05T15:37:01.148396474Z stdout [[2022-07-05 17:37:01]] error: 1 out of 1 tasks failed.
2022-07-05T15:37:01.148347903Z stdout [[2022-07-05 17:37:01]] error: Use -vdebug to see the full traceback.
2022-07-05T15:37:01.148235353Z stdout [[2022-07-05 17:37:01]] error: Unknown error occurred: Not Found
2022-07-05T15:37:01.030566005Z stdout [[2022-07-05 17:37:01]]   - "hjqbrkvn" ("privat")
2022-07-05T15:37:00.891772174Z stdout [[2022-07-05 17:37:00]] local:
2022-07-05T15:37:00.751577839Z stdout [[2022-07-05 17:37:00]] warning: Failed to discover collections for google, use -vdebug to see the full traceback.
2022-07-05T15:37:00.397884203Z stdout [[2022-07-05 17:37:00]] Discovering collections for pair google_local
2022-07-05T15:37:00.205408107Z stdout [[2022-07-05 17:37:00]] crond: USER vdirsyncer pid 148 cmd yes | vdirsyncer -c /vdirsyncer/config discover && vdirsyncer -c /vdirsyncer/config metasync && vdirsyncer -c /vdirsyncer/config sync
2022-07-05T15:36:01.150517508Z stdout [[2022-07-05 17:36:01]] error: 1 out of 1 tasks failed.
2022-07-05T15:36:01.150445998Z stdout [[2022-07-05 17:36:01]] error: Use -vdebug to see the full traceback.
2022-07-05T15:36:01.150325178Z stdout [[2022-07-05 17:36:01]] error: Unknown error occurred: Not Found
2022-07-05T15:36:01.040395877Z stdout [[2022-07-05 17:36:01]]   - "hjqbrkvn" ("privat")
2022-07-05T15:36:00.904075175Z stdout [[2022-07-05 17:36:00]] local:
2022-07-05T15:36:00.754974988Z stdout [[2022-07-05 17:36:00]] warning: Failed to discover collections for google, use -vdebug to see the full traceback.
2022-07-05T15:36:00.396383196Z stdout [[2022-07-05 17:36:00]] Discovering collections for pair google_local
2022-07-05T15:36:00.204823292Z stdout [[2022-07-05 17:36:00]] crond: USER vdirsyncer pid 137 cmd yes | vdirsyncer -c /vdirsyncer/config discover && vdirsyncer -c /vdirsyncer/config metasync && vdirsyncer -c /vdirsyncer/config sync
2022-07-05T15:35:01.186076506Z stdout [[2022-07-05 17:35:01]] error: 1 out of 1 tasks failed.
2022-07-05T15:35:01.185902206Z stdout [[2022-07-05 17:35:01]] error: Use -vdebug to see the full traceback.
2022-07-05T15:35:01.185779085Z stdout [[2022-07-05 17:35:01]] error: Unknown error occurred: Not Found
2022-07-05T15:35:01.062918650Z stdout [[2022-07-05 17:35:01]]   - "hjqbrkvn" ("privat")

Thnx for your help

crond: root: Permission denied

since the last updates I get this error message and no syncing

[[2023-05-05 12:21:26]] crond: crond (busybox 1.35.0) started, log level 8
[[2023-05-05 12:21:26]] crond: root: Permission denied
[[2023-05-05 12:22:00]] crond: root: Permission denied

i already reset my config directory so the permissions are correct on all files.

Update vdirsyncer to latest version : 0.19.1

Hello,
I want to use the last version of vdirsyncer, the 0.19.1.
Can you update your image to have this new version ?
Or add something to let the app update itself after a container restart ?

Thanks in advance.

Strange cron error

Hi,

good work, but I have a strange error, every time I restart the container the cron entry is rewritten. So my crontab now looks like this:

# do daily/weekly/monthly maintenance
# min   hour    day     month   weekday command
*/15    *       *       *       *       run-parts /etc/periodic/15min
0       *       *       *       *       run-parts /etc/periodic/hourly
0       2       *       *       *       run-parts /etc/periodic/daily
0       3       *       *       6       run-parts /etc/periodic/weekly
0       5       1       *       *       run-parts /etc/periodic/monthly

12,42 0,1,7-23 * * * yes | vdirsyncer discover && vdirsyncer metasync && vdirsyncer sync
12,42 0,1,7-23 * * * yes | vdirsyncer discover && vdirsyncer metasync && vdirsyncer sync
12,42 0,1,7-23 * * * yes | vdirsyncer discover && vdirsyncer metasync && vdirsyncer sync
12,42 0,1,7-23 * * * yes | vdirsyncer discover && vdirsyncer metasync && vdirsyncer sync
12,42 0,1,7-23 * * * yes | vdirsyncer discover && vdirsyncer metasync && vdirsyncer sync
12,42 0,1,7-23 * * * yes | vdirsyncer discover && vdirsyncer metasync && vdirsyncer sync
12,42 0,1,7-23 * * * yes | vdirsyncer discover && vdirsyncer metasync && vdirsyncer sync
12,42 0,1,7-23 * * * yes | vdirsyncer discover && vdirsyncer metasync && vdirsyncer sync

greetings

Cronjob not starting - supercronic command executes with no arguments

Issue with Version 2.4.4: (no problem in version 2.4.3)
Hi, many thanks in advance, the documentation is excellent however I did find an issue that I could not solve:
When I launch the docker container the supercronic process does not start (see the log output at below).

In start.sh I see that the command that should run is
/usr/bin/supercronic "${LOG_LEVEL}" "${CRON_FILE}"
but it looks like something is happening to the environment variables such that they are not being added as arguments to the command and so it looks like the command that is actually running is simply:
/usr/bin/supercronic "" ""

When I open a shell into the running container I can see both variables are correctly assigned ($LOG_LEVEL="" as default):

abcdef123456:/vdirsyncer$ echo $LOG_LEVEL

abcdef123456:/vdirsyncer$ echo $CRON_FILE
/etc/crontabs/vdirsyncer
abcdef123456:/vdirsyncer$

I can launch supercronic from inside the running container with this command:

/usr/bin/supercronic $LOG_LEVEL $CRON_FILE

or from outside the container like this:

docker exec vdirsyncer /usr/bin/supercronic /etc/crontabs/vdirsyncer

Either will have the same effect of starting the supercronic process.

I hope that this is helpful for you to improve the project and that I have not made some other mistake and have now wasted your time.

Log output:
[2023-07-13 13:41:04] Welcome to Vdirsyncer DOCKERIZED! :)
[2023-07-13 13:41:04]
[2023-07-13 13:41:04] For more information please visit the official docs page.
[2023-07-13 13:41:04] There you will also find configuration examples.
[2023-07-13 13:41:04] https://vdirsyncer.pimutils.org/en/stable/index.html
[2023-07-13 13:41:04]
[2023-07-13 13:41:04] If you have any problems with Vdirsyncer, please
[2023-07-13 13:41:04] visit the Github repo and open an issue.
[2023-07-13 13:41:04] https://github.com/pimutils/vdirsyncer
[2023-07-13 13:41:04]
[2023-07-13 13:41:04] If there is a problem with the container,
[2023-07-13 13:41:04] contact me or open an issue in my Github repo.
[2023-07-13 13:41:04] https://github.com/Bleala/Vdirsyncer-DOCKERIZED
[2023-07-13 13:41:04] I am trying to fix it, so that everything
[2023-07-13 13:41:04] is running as expected. :)
[2023-07-13 13:41:04]
[2023-07-13 13:41:04] Enjoy!
[2023-07-13 13:41:04]
[2023-07-13 13:41:04] Starting Logging...
[2023-07-13 13:41:04]
[2023-07-13 13:41:04] Old logfile has been deleted.
[2023-07-13 13:41:04]
[2023-07-13 13:41:04] New logfile has been created.
[2023-07-13 13:41:04]
[2023-07-13 13:41:04] Current timezone is Europe/Vienna
[2023-07-13 13:41:04] Current time is Thu Jul 13 13:41:04 CEST 2023
[2023-07-13 13:41:04]
[2023-07-13 13:41:04] Only Autosync is enabled.
[2023-07-13 13:41:04] Usage: /usr/bin/supercronic [OPTIONS] CRONTAB
[2023-07-13 13:41:04]
[2023-07-13 13:41:04] Available options:
[2023-07-13 13:41:04] -debug
[2023-07-13 13:41:04] enable debug logging
[2023-07-13 13:41:04] -json
[2023-07-13 13:41:04] enable JSON logging
[2023-07-13 13:41:04] -overlapping
[2023-07-13 13:41:04] enable tasks overlapping
[2023-07-13 13:41:04] -passthrough-logs
[2023-07-13 13:41:04] passthrough logs from commands, do not wrap them in Supercronic logging
[2023-07-13 13:41:04] -prometheus-listen-address string
[2023-07-13 13:41:04] give a valid ip[:port] address to expose Prometheus metrics at /metrics (port defaults to 9746), use 0.0.0.0 for all network interfaces.
[2023-07-13 13:41:04] -quiet
[2023-07-13 13:41:04] do not log informational messages (takes precedence over debug)
[2023-07-13 13:41:04] -sentry-dsn string
[2023-07-13 13:41:04] enable Sentry error logging, using provided DSN
[2023-07-13 13:41:04] -sentryDsn string
[2023-07-13 13:41:04] alias for sentry-dsn
[2023-07-13 13:41:04] -split-logs
[2023-07-13 13:41:04] split log output into stdout/stderr
[2023-07-13 13:41:04] -test
[2023-07-13 13:41:04] test crontab (does not run jobs)

Log file a little messy: hard to seek what it's important

Hello,
I just check the log of the container, and it's really hard to read.

[2023-06-23 20:41:52] time="2023-06-23T20:41:52+02:00" level=info msg="read crontab: /etc/crontabs/vdirsyncer"
[2023-06-23 21:00:00] time="2023-06-23T21:00:00+02:00" level=info msg=starting iteration=0 job.command="yes | /usr/local/bin/vdirsyncer -c /vdirsyncer/config discover" job.position=0 job.schedule="*/30 * * * *"
[2023-06-23 21:00:00] time="2023-06-23T21:00:00+02:00" level=info msg="Discovering collections for pair icloud_calendar_XXX_to_nextcloud" channel=stderr iteration=0 job.command="yes | /usr/local/bin/vdirsyncer -c /vdirsyncer/config discover" job.position=0 job.schedule="*/30 * * * *"
[2023-06-23 21:00:01] time="2023-06-23T21:00:01+02:00" level=info msg="xxx_icloud_calendar:" channel=stderr iteration=0 job.command="yes | /usr/local/bin/vdirsyncer -c /vdirsyncer/config discover" job.position=0 job.schedule="*/30 * * * *"
[2023-06-23 21:00:01] time="2023-06-23T21:00:01+02:00" level=info msg="  - \"xxxx-xxxx-xxxx-xxxx\" (\"Rappels ⚠️\")" channel=stderr iteration=0 job.command="yes | /usr/local/bin/vdirsyncer -c /vdirsyncer/config discover" job.position=0 job.schedule="*/30 * * * *"
[2023-06-23 21:00:01] time="2023-06-23T21:00:01+02:00" level=info msg="  - \"xxxx-xxxx-xxxx-xxxx"\ (\"iCloud - Pour les Chats 😺\")" channel=stderr iteration=0 job.command="yes | /usr/local/bin/vdirsyncer -c /vdirsyncer/config discover" job.position=0 job.schedule="*/30 * * * *"
[2023-06-23 21:00:01] time="2023-06-23T21:00:01+02:00" level=info msg="  - \"xxxx-xxxx-xxxx-xxxx\" (\"iCloud - Personnel\")" channel=stderr iteration=0 job.command="yes | /usr/local/bin/vdirsyncer -c /vdirsyncer/config discover" job.position=0 job.schedule="*/30 * * * *"
[2023-06-23 21:00:01] time="2023-06-23T21:00:01+02:00" level=info msg="  - \"xxxx-xxxx-xxxx-xxxx\" (\"Rappels - Famille ⚠️\")" channel=stderr iteration=0 job.command="yes | /usr/local/bin/vdirsyncer -c /vdirsyncer/config discover" job.position=0 job.schedule="*/30 * * * *"
[2023-06-23 21:00:01] time="2023-06-23T21:00:01+02:00" level=info msg="  - \"xxxx-xxxx-xxxx-xxxx\" (\"iCloud - Lycée\")" channel=stderr iteration=0 job.command="yes | /usr/local/bin/vdirsyncer -c /vdirsyncer/config discover" job.position=0 job.schedule="*/30 * * * *"
[2023-06-23 21:00:01] time="2023-06-23T21:00:01+02:00" level=info msg="  - \"xxxx-xxxx-xxxx-xxxx\" (\"iCloud - Famille\")" channel=stderr iteration=0 job.command="yes | /usr/local/bin/vdirsyncer -c /vdirsyncer/config discover" job.position=0 job.schedule="*/30 * * * *"
[2023-06-23 21:00:01] time="2023-06-23T21:00:01+02:00" level=info msg="  - \"xxxx-xxxx-xxxx-xxxx\" (\"Ecole et Direction_Cécile\")" channel=stderr iteration=0 job.command="yes | /usr/local/bin/vdirsyncer -c /vdirsyncer/config discover" job.position=0 job.schedule="*/30 * * * *"
[2023-06-23 21:00:03] time="2023-06-23T21:00:03+02:00" level=info msg="xxx_nextcloud_calendar:" channel=stderr iteration=0 job.command="yes | /usr/local/bin/vdirsyncer -c /vdirsyncer/config discover" job.position=0 job.schedule="*/30 * * * *"
[2023-06-23 21:00:03] time="2023-06-23T21:00:03+02:00" level=info msg="  - \"xxxx-xxxx-xxxx-xxxx\" (\"Rappels - Famille ⚠️\")" channel=stderr iteration=0 job.command="yes | /usr/local/bin/vdirsyncer -c /vdirsyncer/config discover" job.position=0 job.schedule="*/30 * * * *"
[2023-06-23 21:00:03] time="2023-06-23T21:00:03+02:00" level=info msg="  - \"xxxx-xxxx-xxxx-xxxx\" (\"Rappels ⚠️\")" channel=stderr iteration=0 job.command="yes | /usr/local/bin/vdirsyncer -c /vdirsyncer/config discover" job.position=0 job.schedule="*/30 * * * *"
[2023-06-23 21:00:03] time="2023-06-23T21:00:03+02:00" level=info msg="  - \"home\" (\"iCloud - Personnel\")" channel=stderr iteration=0 job.command="yes | /usr/local/bin/vdirsyncer -c /vdirsyncer/config discover" job.position=0 job.schedule="*/30 * * * *"

There is too much unwanted information for me...

I had made a script to launch the commands for me, on my mac, checking if the binaries are installed, and here a portion of the log I get:

[2023-06-23 21:30:37] ---- Début des commandes vdirsyncer du jour ----
[2023-06-23 21:30:37]      --> Synchronisation pour MOI :
[2023-06-23 21:30:37]            --   AUTO_DISCOVER est à true :
[2023-06-23 21:30:37]                --   Discovering collections for pair icloud_calendar_XYZ_to_nextcloud
[2023-06-23 21:30:38]                --   xyz_icloud_calendar:
[2023-06-23 21:30:38]                --     - "xxxx-xxxx-xxxx-xxxx" ("Rappels ⚠️")
[2023-06-23 21:30:38]                --     - "xxxx-xxxx-xxxx-xxxx" ("iCloud - XYZ")
[2023-06-23 21:30:38]                --     - "xxxx-xxxx-xxxx-xxxx" ("iCloud - Personnel")
[2023-06-23 21:30:38]                --     - "xxxx-xxxx-xxxx-xxxx" ("Rappels - Famille ⚠️")
[2023-06-23 21:30:38]                --     - "xxxx-xxxx-xxxx-xxxx" ("iCloud - Famille")
[2023-06-23 21:30:38]                --     - "xxxx-xxxx-xxxx-xxxx" ("iCloud - Pour les Chats 😺")
[2023-06-23 21:30:39]                --     - "xxxx-xxxx-xxxx-xxxx" ("Ecole et XYZ-XYZ")
[2023-06-23 21:30:39]                --   xyz_nextcloud_calendar:
[2023-06-23 21:30:39]                --     - "xxxx-xxxx-xxxx-xxxx" ("Rappels - Famille ⚠️")
[2023-06-23 21:30:40]                --     - "xxxx-xxxx-xxxx-xxxx" ("iCloud - XYZ")
[2023-06-23 21:30:40]                --     - "xxxx-xxxx-xxxx-xxxx" ("iCloud - Pour les Chats 😺")
[2023-06-23 21:30:40]                --     - "xxxx-xxxx-xxxx-xxxx" ("Ecole et XYZ-XYZ")
[2023-06-23 21:30:40]                --     - "xxxx-xxxx-xxxx-xxxx" ("Rappels ⚠️")
[2023-06-23 21:30:40]                --     - "xxxx-xxxx-xxxx-xxxx" ("iCloud - Personnel")
[2023-06-23 21:30:40]                --     - "xxxx-xxxx-xxxx-xxxx" ("iCloud - Famille")
[2023-06-23 21:30:40]                --   Saved for icloud_calendar_XYZ_to_nextcloud: collections = ["iCloud_Lycee", "iCloud_chats", "iCloud_Personnel", "iCloud_Famille", "Rappels", "Rappels_Famille", "xyz-XYZ-xyz"]
[2023-06-23 21:30:40]            --   Metasyncing icloud_calendar_XYZ_to_nextcloud/iCloud_Lycee
[2023-06-23 21:30:40]            --   Metasyncing icloud_calendar_XYZ_to_nextcloud/iCloud_chats
[2023-06-23 21:30:40]            --   Metasyncing icloud_calendar_XYZ_to_nextcloud/iCloud_Personnel
[2023-06-23 21:30:40]            --   Metasyncing icloud_calendar_XYZ_to_nextcloud/iCloud_Famille
[2023-06-23 21:30:40]            --   Metasyncing icloud_calendar_XYZ_to_nextcloud/Rappels
[2023-06-23 21:30:40]            --   Metasyncing icloud_calendar_XYZ_to_nextcloud/Rappels_Famille
[2023-06-23 21:30:40]            --   Metasyncing icloud_calendar_XYZ_to_nextcloud/xyz-XYZ-xyz
[2023-06-23 21:30:43]            --   Syncing icloud_calendar_XYZ_to_nextcloud/iCloud_Lycee
[2023-06-23 21:30:43]            --   Syncing icloud_calendar_XYZ_to_nextcloud/iCloud_chats
[2023-06-23 21:30:43]            --   Syncing icloud_calendar_XYZ_to_nextcloud/iCloud_Personnel
[2023-06-23 21:30:43]            --   Syncing icloud_calendar_XYZ_to_nextcloud/iCloud_Famille
[2023-06-23 21:30:43]            --   Syncing icloud_calendar_XYZ_to_nextcloud/Rappels
[2023-06-23 21:30:43]            --   Syncing icloud_calendar_XYZ_to_nextcloud/Rappels_Famille
[2023-06-23 21:30:43]            --   Syncing icloud_calendar_XYZ_to_nextcloud/xyz-XYZ-xyz
[2023-06-23 21:30:44]      --> Fin de la synchronisatinon pour MOI.

Here a portion of what generate the log (I was greatly inspired by your work for the ts and tee commands ^^ except I use touch instead of curl to create the logfile.)

for user in "${user_list[@]}"; do
    config_full_path="${config_path}/config_${user}"
    printf "     --> Synchronisation pour %s :\n" "${user}" 2>&1 | ts '[%Y-%m-%d %H:%M:%S]' | tee -a "${LOG_FILE}"

    # Commande à lancer manuellement dans un terminal :
    #           vdirsyncer -v INFO --config ~/"Gitea/Scripts--Powershell-et-Bash-ZSH/Scripts-macOS/Vdirsyncer-configs/config_ME" discover      /// metasync | sync
    #           vdirsyncer -v INFO --config ~/"Gitea/Scripts--Powershell-et-Bash-ZSH/Scripts-macOS/Vdirsyncer-configs/config_HER" discover     /// metasync | sync
    if [[ "${AUTO_DISCOVER}" == "true" ]]; then
        printf "AUTO_DISCOVER est à true :\n" 2>&1         | ts "[%Y-%m-%d %H:%M:%S]            --  " | tee -a "${LOG_FILE}"
        vdirsyncer -v INFO --config "${config_full_path}" discover  2>&1    | ts "[%Y-%m-%d %H:%M:%S]                --  " | tee -a "${LOG_FILE}"
    fi
    vdirsyncer -v INFO --config "${config_full_path}" metasync  2>&1    | ts "[%Y-%m-%d %H:%M:%S]            --  " | tee -a "${LOG_FILE}"
    vdirsyncer -v INFO --config "${config_full_path}" sync 2>&1         | ts "[%Y-%m-%d %H:%M:%S]            --  " | tee -a "${LOG_FILE}"
    printf "     --> Fin de la synchronisation pour %s.\n" "${user}" 2>&1 | ts '[%Y-%m-%d %H:%M:%S]' | tee -a "${LOG_FILE}"
done

If you could do something, it would be great. And I can get put definitively vdirsyncer on my NAS with docker.

Multiples vulnerabilites

Hello,
I found times to retry your docker image :)
But Docker says that there is some vulnerabilities:
image

Can you update those packages?

Thanks in advance.

Sync problem?

Hi, Thanks for the updated docker image. This is great!
However I have one small problem. It seels only discovery runs, eventhough I have set the flag to true.

Docker composer:

vdirsyncer:
 # image: pschlieker/vdirsyncer-docker
    image: bleala/vdirsyncer:latest
    container_name: vdirsyncer
    volumes:
      - "/share/Docker/vdirsyncer:/vdirsyncer" 
      - "/share/Docker/vdirsyncer/config:/vdirsyncer/config"
      
      - "/etc/localtime:/etc/localtime:ro"  
    environment: 
      - CRON_TIME=0 */1 * * *
      - AUTODISCOVER=true
      - AUTOSYNC=true
    restart: unless-stopped
    networks:
      docker_frontend:

In the log it confirms the correct piece of the script is running:

Starting Logging...

Autodiscover and Autosync are enabled


crond: crond (busybox 1.33.1) started, log level 8


crond: USER root pid  92 cmd run-parts /etc/periodic/15min


crond: USER root pid 200 cmd run-parts /etc/periodic/15min


crond: USER root pid 296 cmd run-parts /etc/periodic/15min


crond: USER root pid 402 cmd run-parts /etc/periodic/15min


crond: USER root pid 403 cmd run-parts /etc/periodic/hourly


crond: USER root pid 404 cmd yes | vdirsyncer discover && vdirsyncer metasync && vdirsyncer sync

It runs the discovery, however not the meta or the sync?

After the discovery has run (I will not post the log as this contains personal names etc.) this happens.

error: 1 out of 11 tasks failed.


crond: USER root pid 512 cmd run-parts /etc/periodic/15min


crond: USER root pid 616 cmd run-parts /etc/periodic/15min


crond: USER root pid 716 cmd run-parts /etc/periodic/15min


crond: USER root pid 820 cmd run-parts /etc/periodic/15min


crond: USER root pid 821 cmd run-parts /etc/periodic/hourly


crond: USER root pid 822 cmd yes | vdirsyncer discover && vdirsyncer metasync && vdirsyncer sync

Same problem over again...

The error is due to a sync problem with sogo, so I would not expect this to be a problem?

It doesnt seem like this is correct behaviour?

log file is overwritten at each container remake

Hi (again),

You generate the logfile when the container is created, however when the container is recreated (in order to read the new configfile) the logfile is overwritten by an empty file. Perhaps rename the old file?

/Benjamin

usage of non-root user for container and generated outputs

Hi,

The application inside container seems to run as root user. All generated output files (e.g., ics calendar files) are owned by the user root.
Would it be possible to change to a non-root user?

Best practice is to define the user and group as an environment variable for the Vdirsyncer container (as far I know).

Would be great to have this option, because another program cannot use the ics file because he is not root (and setting the file permission once does not help).

Thanks for dockerizing it.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.