-
Notifications
You must be signed in to change notification settings - Fork 147
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
[ENHANCEMENT] Convert containers to releases #574
Comments
I also have a similar requirement, which I could use for rolling deployments of apps. To base this feature on releases is perhaps a bit hard:
Alternative idea for this is using clones (assuming spawned childs jails/containers are disposable)
I don't know if @cedwards has any ideas (or plans) for this subject? (Btw thank you very much for BastilleBSD, I really like it, and also the effort that has been put in this project!!) |
Cant the Bastille clone command be used to do something like this? |
Yeah I was thinking about that to. A 'zfs-clone' clone as an alternative option to the current copy (send/recv) clone. (With clear warning it's a zfs clone. This is not usually what you want when copying a jail by default) |
Bastille now includes a --no-validate flag on creation. This means that you can base your jail on any RELEASE of directory as long as it is inside the $releases directory. Have you tried this? |
Is your feature request related to a problem? Please describe.
I'm thinking about using Bastille to support horizontal scaling; spinning up new containers of the same app to service increased traffic possibly load balanced via Consul.
Describe the solution you'd like
Once a container is configured allow it to be converted into a release so future instances can be spun up as thin jails quickly.
Describe alternatives you've considered
Thought about running templates to bare releases but stil too slow installing packages and all. Scaling is too slow.
Additional context
The text was updated successfully, but these errors were encountered: