You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm trying out Tern as a way to provide package details alongside the container for transparency and to better comply with license requirements. (The current report doesn't seem sufficient to comply with attribution requirements of most licenses, but that might improve in the future.) What would be the best way to publish the report alongside the resulting container? I'm using Tern as part of the build process. I thought to build a new container that adds the Tern report to the workdir and publishes this new container instead. In this way the information is available through the normal container interfaces and there is no need to setup a different method of publication.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I'm trying out Tern as a way to provide package details alongside the container for transparency and to better comply with license requirements. (The current report doesn't seem sufficient to comply with attribution requirements of most licenses, but that might improve in the future.) What would be the best way to publish the report alongside the resulting container? I'm using Tern as part of the build process. I thought to build a new container that adds the Tern report to the workdir and publishes this new container instead. In this way the information is available through the normal container interfaces and there is no need to setup a different method of publication.
Beta Was this translation helpful? Give feedback.
All reactions