Open GuyKh opened 3 years ago
Docker container fails to start;
After initialization it shoots the following errors in the Docker Logs:
Current thread 0x76fc7390 (most recent call first): <no Python frame> 7889-11-12-01:56:40 [STARTING] ** [monitoring] [1] Starting Zabbix Agent (modern) 5.4.2 7889-09-19-00:35:36 [STARTING] ** [traefik-cloudflare-companion] [2] Starting Traefik Cloudflare Companion Fatal Python error: pyinit_main: can't initialize time Python runtime state: core initialized PermissionError: [Errno 1] Operation not permitted
Run on RaspberryPi3 (Armv7).
Should start
Recreating cf-companion ... done [s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] 00-functions: applying... [fix-attrs.d] 00-functions: exited 0. [fix-attrs.d] 01-s6: applying... [fix-attrs.d] 01-s6: exited 0. [fix-attrs.d] 02-zabbix: applying... [fix-attrs.d] 02-zabbix: exited 0. [fix-attrs.d] 03-logrotate: applying... [fix-attrs.d] 03-logrotate: exited 0. [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] 00-startup: executing... [cont-init.d] 00-startup: exited 0. [cont-init.d] 01-timezone: executing... [cont-init.d] 01-timezone: exited 0. [cont-init.d] 02-permissions: executing... [cont-init.d] 02-permissions: exited 0. [cont-init.d] 03-monitoring: executing... 7889-11-19-08:08:24 [NOTICE] ** [monitoring] Container configured for monitoring with 'zabbix modern' [cont-init.d] 03-monitoring: exited 0. [cont-init.d] 04-scheduling: executing... 7889-09-14-17:59:20 [NOTICE] ** [scheduling] Disabling Scheduling [cont-init.d] 04-scheduling: exited 0. [cont-init.d] 05-logging: executing... /var/run/s6/etc/cont-init.d/05-logging: line 11: /assets/cron//logrotate: No such file or directory 7889-09-08-06:06:48 [NOTICE] ** [logging] Disabling Log Shipping Functionality [cont-init.d] 05-logging: exited 0. [cont-init.d] 06-messaging: executing... 7889-10-01-02:12:08 [NOTICE] ** [messaging] Container configured to route mail via SMTP to 'postfix-relay' [cont-init.d] 06-messaging: exited 0. [cont-init.d] 10-cloudflare-companion: executing... [cont-init.d] 10-cloudflare-companion: exited 0. [cont-init.d] 99-container: executing... [cont-init.d] 99-container: exited 0. [cont-init.d] done. [services.d] starting services [services.d] done. 7889-10-24-08:29:12 [STARTING] ** [traefik-cloudflare-companion] [1] Starting Traefik Cloudflare Companion Fatal Python error: pyinit_main: can't initialize time Python runtime state: core initialized PermissionError: [Errno 1] Operation not permitted Current thread 0x76fc7390 (most recent call first): <no Python frame> 7889-11-12-01:56:40 [STARTING] ** [monitoring] [1] Starting Zabbix Agent (modern) 5.4.2 7889-09-19-00:35:36 [STARTING] ** [traefik-cloudflare-companion] [2] Starting Traefik Cloudflare Companion Fatal Python error: pyinit_main: can't initialize time Python runtime state: core initialized PermissionError: [Errno 1] Operation not permitted Current thread 0x76f68390 (most recent call first): <no Python frame> 7889-10-30-03:34:48 [STARTING] ** [traefik-cloudflare-companion] [3] Starting Traefik Cloudflare Companion Fatal Python error: pyinit_main: can't initialize time Python runtime state: core initialized PermissionError: [Errno 1] Operation not permitted
cf-companion: container_name: cf-companion image: tiredofit/traefik-cloudflare-companion:latest restart: always volumes: - /var/run/docker.sock:/var/run/docker.sock:ro environment: - TIMEZONE=$TZ - TRAEFIK_VERSION=2 - CF_EMAIL=$CLOUDFLARE_EMAIL # Same as traefik - CF_TOKEN=$CLOUDFLARE_API_KEY # Same as traefik - TARGET_DOMAIN=$DOMAINNAME - DOMAIN1=$DOMAINNAME - DOMAIN1_ZONE_ID=$CLOUDFLARE_ZONEID # Copy from Cloudflare Overview page - DOMAIN1_PROXIED=TRUE
I read online that libseccomp2 should be updated, but I'm not sure. https://github.com/linuxserver/docker-calibre-web/issues/119
A working workaround exists here: https://blog.samcater.com/fix-workaround-rpi4-docker-libseccomp2-docker-20/
Summary
Docker container fails to start;
After initialization it shoots the following errors in the Docker Logs:
Steps to reproduce
Run on RaspberryPi3 (Armv7).
What is the expected correct behavior?
Should start
Relevant logs and/or screenshots
Environment
Possible fixes
I read online that libseccomp2 should be updated, but I'm not sure. https://github.com/linuxserver/docker-calibre-web/issues/119
A working workaround exists here: https://blog.samcater.com/fix-workaround-rpi4-docker-libseccomp2-docker-20/