Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Harvesting might be broken in latest deployment #75

Open
1 task done
hcvdwerf opened this issue Jul 5, 2024 · 0 comments
Open
1 task done

Harvesting might be broken in latest deployment #75

hcvdwerf opened this issue Jul 5, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@hcvdwerf
Copy link

hcvdwerf commented Jul 5, 2024

🔄 Duplicate Check

  • 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

  1. 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

📸 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

@hcvdwerf hcvdwerf added the bug Something isn't working label Jul 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant