[BUG] Customizable crontabs broken

[DatBoiTroy]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

The container image doesn't recognize modified crontab files located in /config/crontabs to override the default crontabs.

Expected Behavior

S6 overlay service "init-crontab-config", inherited from the baseimage-alpine image, should create custom user crontabs at /config/crontabs, copied from /default/crontabs, when they do not already exist. The content of the custom crontabs is then loaded into the crontabs of the container users.

#343 moves the default crontab files from /default/crontabs to /etc/crontabs. The S6 "init-crontab-config" service checks for the existence of "/defaults/crontabs/${cron_user}" before creating and/or loading the custom crontab file, so the inside code never executes to do so.

Steps To Reproduce

Present from a fresh docker run. Nothing in particular to produce this issue.

Environment

- OS: Ubuntu 24.04.3 LTS
- How docker service was installed: Official Docker Repo

CPU architecture

x86-64

Docker creation

---
services:
  # Nextcloud cloud storage manager
  nextcloud:
    image: "lscr.io/linuxserver/nextcloud:32.0.3"
    container_name: nextcloud
    hostname: nextcloud
    environment:
      TZ: Etc/UTC
      PUID: "65534"
      PGID: "65534"
    volumes:
      - nextcloud_config:/config
      - /mnt/nfs/nextcloud/data:/data
    logging:
      driver: json-file
      options:
        max-file: "3"
        max-size: 3m
    depends_on:
      - nextcloud_db
    restart: unless-stopped

  # Nextcloud PostgreSQL server
  nextcloud_db:
    image: "postgres:18.1-alpine3.23"
    container_name: nextcloud_db
    hostname: nextcloud_db
    environment:
      TZ: Etc/UTC
      POSTGRES_USER: XXXXXXXXXXXXXX
      POSTGRES_PASSWORD: 'XXXXXXXXXXXXXX'
      POSTGRES_DB: XXXXXXXXXXXXX
    volumes:
      - nextcloud_db_data:/var/lib/postgresql
    logging:
      driver: json-file
      options:
        max-file: "3"
        max-size: 3m
    restart: unless-stopped

volumes:
  nextcloud_config:
    driver: local
  nextcloud_db_data:
    driver: local

Container logs

[migrations] started
[migrations] 01-nginx-site-confs-default: skipped
[migrations] 02-default-location: skipped
[migrations] done
───────────────────────────────────────

      ██╗     ███████╗██╗ ██████╗
      ██║     ██╔════╝██║██╔═══██╗
      ██║     ███████╗██║██║   ██║
      ██║     ╚════██║██║██║   ██║
      ███████╗███████║██║╚██████╔╝
      ╚══════╝╚══════╝╚═╝ ╚═════╝

   Brought to you by linuxserver.io
───────────────────────────────────────

To support LSIO projects visit:
https://www.linuxserver.io/donate/

───────────────────────────────────────
GID/UID
───────────────────────────────────────

User UID:    65534
User GID:    65534
───────────────────────────────────────
Linuxserver.io version: 32.0.3-ls409
Build-date: 2025-12-23T11:53:53+00:00
───────────────────────────────────────

using keys found in /config/keys
Initializing nextcloud 32.0.3.2 (this can take a while) ...
Setting permissions
Initializing finished
[custom-init] No custom files found, skipping...
[ls.io-init] done.

[github-actions]

Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.

[aptalca]

https://info.linuxserver.io/issues/2023-11-02-cron/

[DatBoiTroy]

https://info.linuxserver.io/issues/2023-11-02-cron/

I guess I missed this when I started researching the problem. Thank you... that explains why this behavior is expected and provides a solution.