Starting the container with pre-existing local.cf fails sa-update

[keyoke]

Summary

Starting the container with pre-existing local.cf fails sa-update

Steps to reproduce

1. setup docker-compose file, see below excerpt
   spamassassin:
   image: spamassassin:v2.0.11
   restart: unless-stopped
   volumes:
   - spamassassin-logs:/logs
   - spamassassin-config:/config
   - spamassassin-data:/data
   volumes:
   spamassassin-logs:
   driver: local
   driver_opts:
   type: 'none'
   o: 'bind'
   device: '/opt/smf/var/log/spamassassin'
   spamassassin-config:
   driver: local
   driver_opts:
   type: 'none'
   o: 'bind'
   device: '/opt/smf/etc/spamassassin'
   spamassassin-data:
   driver: local
   driver_opts:
   type: 'none'
   o: 'bind'
   device: '/opt/smf/var/lib/spamassassin'
2. Create initial /opt/smf/etc/spamassassin/local.cf file with following contents
   dns_available yes
   report_contact postmaster@mydomain.com
   report_hostname mail.mydomain.com
   rewrite_header Subject [SPAM]
   report_safe 1
   required_score 8.0
   use_bayes 1
   bayes_auto_learn 1
3. docker compose up
4. docker compose exec -it spamaassassin
5. sa-update

What is the expected correct behavior?

spamassassin should load config and update rules on initial start

Relevant logs and/or screenshots

[tiredofit/alpine:7.8.35 09:58:45 /] $ sa-update
config: no configuration text or files found! do you need to run 'sa-update'?
Timeout::_run: check: no loaded plugin implements 'check_main': cannot scan!
Check that the necessary '.pre' files are in the config directory.
At a minimum, v320.pre loads the Check plugin which is required.

Environment

• Image version / tag: 2.0.11
• Host OS: ubuntu 22.04

Possible fixes