Releases · puniverse/capsule-shield

Breaking changes

Many option and attribute names have been generalized and shortened for user's convenience, refer to the README for a complete list.
Options to disable TTYs and choose a different network type from veth have been removed as they'll undergo major revision and generalisation in the forthcoming releases.
The container's home is now found outside of Capsule's cache, in ${user.home}/.capsule-shield/<ID>, in order to avoid permission-related issues.

Links: assign IDs to your capsule containers and refer them from your applications running inside them.
Log forwarding: by default all your application logs will be redirected to the host capsule process. Log4J, Log4J2, SLF4J, JCL and JUL are supported.
JMX forwarding: just connect to your host capsule process to manage your application running in the container.
The runtime contained ID can now be chosen as different from the app ID; this allows more convenient links as well as running the same capsule in different containers simultaneously.
A static IP can now be assigned to the container in addition to using DHCP.
The default gateway can now be explicitly set to ensure Internet connectivity for the application running in the container.
A new option allows simply destroying a container without starting it afterwards.