New ask Hacker News story: Ask HN: How do you handle LICENSE notices in published Docker images?
Ask HN: How do you handle LICENSE notices in published Docker images?
3 by mrmattyboy | 0 comments on Hacker News.
Hey all :) I was put off releasing a pre-built docker image for an open source project, mainly due to mess of licenses that is Docker. I finally decided to do it by doing the following (for a Python-based application): * Create a LICENSE.third-party file, containing information about where to find LICENSES for the installed third-party applications (https://ift.tt/kSzemHI) * Use pip-licenses to generate per-package license files for each of the installed pip packages (https://ift.tt/ONR3SsZ) * Copied all 'doc' license files from deb packages to common directory (https://ift.tt/RJ89h0a) * Manually copy licenses for tooling that is installed in the Docker build (https://ift.tt/xgBzlfi) I'm wondering if anyone else has tackled this and/or seen it done anywhere else? How have others implemented anything similar? Thanks! :)
3 by mrmattyboy | 0 comments on Hacker News.
Hey all :) I was put off releasing a pre-built docker image for an open source project, mainly due to mess of licenses that is Docker. I finally decided to do it by doing the following (for a Python-based application): * Create a LICENSE.third-party file, containing information about where to find LICENSES for the installed third-party applications (https://ift.tt/kSzemHI) * Use pip-licenses to generate per-package license files for each of the installed pip packages (https://ift.tt/ONR3SsZ) * Copied all 'doc' license files from deb packages to common directory (https://ift.tt/RJ89h0a) * Manually copy licenses for tooling that is installed in the Docker build (https://ift.tt/xgBzlfi) I'm wondering if anyone else has tackled this and/or seen it done anywhere else? How have others implemented anything similar? Thanks! :)
Comments
Post a Comment