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

Tooling and processes to ensure licensing requirements for Docker images are satisfied #539

Closed
jlewi opened this issue Dec 9, 2019 · 4 comments · Fixed by #569
Closed

Comments

@jlewi
Copy link
Contributor

jlewi commented Dec 9, 2019

We need tooling and processes to ensure that all the docker images we publish satisfy appropriate licensing requirements.

This is critical for 1.0

To begin with I think we can focus on docker images for applications going 1.0 with Kubeflow 1.0. I think we basically have two kinds of docker images

  1. Docker images corresponding to python binaries
  2. Docker images corresponding to go binaries

For each of these binaries we need to transitively pull all third party dependencies and ensure we satisfy licensing requirements.

@Bobgy
Copy link
Contributor

Bobgy commented Dec 10, 2019

Made PR for tools for automating go dependencies' licenses: #540

@jlewi
Copy link
Contributor Author

jlewi commented Dec 16, 2019

@zhenghuiwang could you provide an update on this?

@zhenghuiwang
Copy link
Contributor

Update:

Filed several issues above.

For Golang image: follow these instructions to add license files.

For NodeJS image: follow these instructions to add license files.

@jlewi
Copy link
Contributor Author

jlewi commented Jan 21, 2020

@zhenghuiwang can we close this issue or is there more work to be done?

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

Successfully merging a pull request may close this issue.

3 participants