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

Celery beat broken #233

Closed
sas1024 opened this issue Jun 24, 2022 · 1 comment
Closed

Celery beat broken #233

sas1024 opened this issue Jun 24, 2022 · 1 comment

Comments

@sas1024
Copy link
Contributor

sas1024 commented Jun 24, 2022

Hello!
In docker image with superset 1.4.1 celery beat works as expected, but in docker image with superset 1.5.1 it fails with error Permission denied: 'celerybeat-schedule'

As I understand it, the problem is that /home/superset owned by root in docker image with superset 1.5.1.
Celery beat try to create celerybeat-schedule directory, but fails, because docker image run under superset user, but /home/superset (this is WORKDIR of docker image) owned by root.

May be this problem appeared after Dockerfile refactoring.

@amancevice
Copy link
Owner

thanks for raising this, a new version with fixed home dir permissions is on its way

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants