Add support for postBuildAdmin
See original GitHub issueProposed change
In addition to postBuild
script (userspace) also process postBuildAdmin
scripts (system space).
Alternative options / Who would use this feature?
See discussions in #487 and https://gitter.im/jupyterhub/binder?at=5fce35b6fb7f155587ad481a
Issue Analytics
- State:
- Created 3 years ago
- Comments:23 (12 by maintainers)
Top Results From Across the Web
Untitled
How to Create Service in Angular 14? https://www.itsolutionstuff.com/post/how-to-add-hours-to-date-in-pythonexample.html 1.0 2022-06-16T04:46:52+00:00 daily ...
Read more >Add support for postBuildAdmin #1009 - bytemeta
It creates a (micro-scale) separation of concerns. Here, separating all potentially image-breaking specifications (image-breaking because of either not being ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I’m likely going to fork this and allow for base image selection as well. The images that are being minted by repo2docker for our use case are enormous with no common layers. Having the ability to use our “stock” (docker-stack + special sauce) base images will greatly decrease pull/startup time as each user gets a dedicated node that comes with our base images.
I think part of the issue is that repo2docker allows you to install operating system packages using
apt
, and since it’s at the OS level that means it’s often only configurable by root. As an aside, there’s another future problem here- if the base image is upgraded from https://github.com/jupyterhub/repo2docker/blob/cb4621f2544efba496f6cf58f6684846d7c49643/repo2docker/buildpacks/base.py#L18 to the next LTS then since packages may have been dropped or undergone breaking changes this could result in binder repositories failing to build or run.Compare this with most (maybe all?) of the other buildpacks which can be run as a non-admin.