-
Notifications
You must be signed in to change notification settings - Fork 479
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
Set the docker user to tusd. #282
Conversation
@kiloreux looks good to you? |
Thank you for this change. I am not Docker expert so would you mind explaining if it's actually necessary to have a dedicated tusd user inside the Docker container? Does that provide a benefit or makes the setup just more complicated? |
Look good to me. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you.
@kiloreux, thanks for approving my pr. Who is managing the docker account? Looks like there is no autobuild in place, as the new version has not been built yet. |
We manage the tusproject/tusd Docker image and it has autobuilds enabled but they are currently failing: https://cloud.docker.com/u/tusproject/repository/registry-1.docker.io/tusproject/tusd/builds/68adb8d5-e08e-4f0e-8630-1de78eb9e617 Since I don't have the time to look into this currently, would you mind giving the failing Docker build a try? That would help us a lot. |
Thanks for your feedback. I'd be happy to help. Unfortunately, I'm only getting a 404. Maybe because I have no permissions to the repo? My username at docker hub is thirsch as well. |
Good call, thank you very much! I added you to tusproject/tusd, so you should be able to access the build output. Does it work for you now? |
User tusd has been created but is not selected for the tusd process within the container. Fixed in this Dockerfile.