-
Notifications
You must be signed in to change notification settings - Fork 103
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
[feat]: Build a base build image on install, have custom images 'FROM' that. #277
Comments
Izak88
added a commit
to Izak88/abstruse
that referenced
this issue
Nov 10, 2017
Izak88
added a commit
to Izak88/abstruse
that referenced
this issue
Nov 10, 2017
Izak88
added a commit
to Izak88/abstruse
that referenced
this issue
Nov 10, 2017
Izak88
added a commit
to Izak88/abstruse
that referenced
this issue
Nov 13, 2017
Izak88
added a commit
to Izak88/abstruse
that referenced
this issue
Nov 13, 2017
Izak88
added a commit
to Izak88/abstruse
that referenced
this issue
Nov 13, 2017
jkuri
pushed a commit
that referenced
this issue
Nov 14, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Perhaps, upon install, abstruse should build a base image containing all the things it needs to function as a build image (everything between the lines). This image should then be shown in the standard images UI as a "special" image that can be rebuilt and edited if the users want.
The "create new image" dialog should show something like
In order to prevent the user accidentally breaking the image (maybe by overriding the CMD) some sanitisation checks should be in place so that when they save they can be prompted that what they're doing may break things (but not disallow those changes as they 'may' know what they're doing i.e. include the 'entry.sh' script in their own scripts)
The text was updated successfully, but these errors were encountered: