[X] I have searched both open and closed issues and found no similar reports.
đ What Happened?
The latest CKAN docker image (2.10.4) does not start the supervisor or crond anymore. This may cause harvesting to be broken. The previous version, 2.10.3, appears to be fine.
There are no obvious changes in the ckan-base-docker repository. We need to investigate if these issues happen in prod then fix them.
CKAN is going to switch to Debian-based Docker images so we could also switch over and fix it in the new environment.
đŖ Steps to Reproduce
docker compose build will lead to
=> ERROR [ckan-dev internal] load metadata for docker.io/ckan/ckan-dev:2.10.4 1.0s
Adding platform platform: linux/amd64 to docker compose will fix this error, but cron job are not started
đ Duplicate Check
đ What Happened?
The latest CKAN docker image (2.10.4) does not start the supervisor or crond anymore. This may cause harvesting to be broken. The previous version, 2.10.3, appears to be fine. There are no obvious changes in the ckan-base-docker repository. We need to investigate if these issues happen in prod then fix them. CKAN is going to switch to Debian-based Docker images so we could also switch over and fix it in the new environment.
đŖ Steps to Reproduce
=> ERROR [ckan-dev internal] load metadata for docker.io/ckan/ckan-dev:2.10.4 1.0sAdding platform platform: linux/amd64 to docker compose will fix this error, but cron job are not startedđ¸ Screenshots
No response
đ Logs
No response
đ Affected Browsers
No response
đģ Operating System
No response
đ¤ Want to Contribute to the Fix?
No, I can't contribute.
âšī¸ Additional Information
Revert it back to 2.10.3 fix this issue