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

/start_datahub_actions.sh: datahub-actions: command not found in v0.0.18 #121

Open
tom-webber opened this issue Jul 24, 2024 · 7 comments
Open

Comments

@tom-webber
Copy link

tom-webber commented Jul 24, 2024

Deploying the v0.0.18 image on our platform causes a failure as so (we must run the container as non-root):

2024/07/23 16:18:45 Waiting for: http://datahub-datahub-gms:8080/health
2024/07/23 16:18:45 Received 200 from http://datahub-datahub-gms:8080/health
touch: cannot touch '/tmp/datahub/logs/actions/actions.out': Permission denied
No user action configurations found. Not starting user actions.
/start_datahub_actions.sh: line 68: datahub-actions: command not found
2024/07/23 16:18:45 Command exited with error: exit status 127
Stream closed EOF for data-platform-datahub-catalogue-dev/datahub-acryl-datahub-actions-78b977cb6b-fxsmn (acryl-datahub-actions)

The fatal issue appears to be reported by

/start_datahub_actions.sh: line 68: datahub-actions: command not found

which is this part of docker/datahub-actions/start.sh

else
    datahub-actions actions $config_files
fi

Which seems to suggest that datahub-actions is not installed, perhaps indicating that there's some issue with the pip cache. Speculation: perhaps related to the recent addition of USER root?

Side note:
touch: cannot touch '/tmp/datahub/logs/actions/actions.out': Permission denied is not new. It is currently showing in the deployed v0.0.15 pod, so is not introduced in v0.0.18.

Version notes:

  • Stably running v0.13.3 DataHub with v0.0.15 datahub-actions before trying out v0.0.18
@jjoyce0510
Copy link
Contributor

Thanks for reporting this. Pretty uncertain why that root user change would have caused this. To confirm, 0.0.17 is the final working version?

@tom-webber
Copy link
Author

tom-webber commented Jul 30, 2024 via email

Copy link

This issue is stale because it has been open for 30 days with no activity. If you believe this is still an issue on the latest DataHub release please leave a comment with the version that you tested it with. If this is a question/discussion please head to https://slack.datahubproject.io. For feature requests please use https://feature-requests.datahubproject.io

@github-actions github-actions bot added the stale label Aug 30, 2024
@hsheth2
Copy link
Contributor

hsheth2 commented Sep 26, 2024

I haven't really been able to repro this

For example, this works fine for me - even though it runs as non-root

docker run --rm -it --user datahub --entrypoint sh acryldata/datahub-actions:v0.0.18 -c 'datahub-actions actions --help'

Is your setup messing with the PATH env variable at all?

@github-actions github-actions bot removed the stale label Sep 26, 2024
Copy link

This issue is stale because it has been open for 30 days with no activity. If you believe this is still an issue on the latest DataHub release please leave a comment with the version that you tested it with. If this is a question/discussion please head to https://slack.datahubproject.io. For feature requests please use https://feature-requests.datahubproject.io

@github-actions github-actions bot added the stale label Oct 27, 2024
@ELCapitanLLNL
Copy link

Hello,
I am getting same issue with version: docker.io/acryldata/datahub-actions:v0.1.1

Log:

2024/11/05 20:17:55 Ready: http://datahub-datahub-gms:8080/health.
touch: cannot touch '/tmp/datahub/logs/actions/actions.out': Permission denied
ls: cannot access '/etc/datahub/actions/conf/': No such file or directory
No user action configurations found. Not starting user actions.
/start_datahub_actions.sh: line 68: datahub-actions: command not found

@github-actions github-actions bot removed the stale label Nov 6, 2024
@kevin-astrafy
Copy link

I just upgraded to datahub 0.14.1 which also upgraded the datahub-action from 0.0.15 to 0.1.1 and i'm getting the same issue described above. I had to revert the datahub-action image to 0.0.15 to be able to deploy it via the helm chart

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

5 participants