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
We want to benefit as much as possible from upstream fixes in Jupyter's core docker stacks, but also be able to inherit from our own base image so we can fix our own layers in a minimal number of locations. Right now, our base image inherits from deep in the core docker stack tree.
I'm wondering if we should use a mixin approach so we can benefit from upstream fixes to the whole tree without pushing our base image to a leaf node. This will allow us to extend from multiple locations in the core tree while preserving common config of our own.
The text was updated successfully, but these errors were encountered:
We want to benefit as much as possible from upstream fixes in Jupyter's core docker stacks, but also be able to inherit from our own base image so we can fix our own layers in a minimal number of locations. Right now, our base image inherits from deep in the core docker stack tree.
I'm wondering if we should use a mixin approach so we can benefit from upstream fixes to the whole tree without pushing our base image to a leaf node. This will allow us to extend from multiple locations in the core tree while preserving common config of our own.
The text was updated successfully, but these errors were encountered: