Headless Ubuntu/Xfce containers with VNC/noVNC (G3v5).
This is a maintenance release.
.bashrc
is created earlier (stage merge_stage_vnc
)example-secrets.rc
FORCE_BUILDING
and FORCE_PUBLISHING_BUILDER_REPO
(unset means 0
)Added file $HOME/.bashrc
to all images.
It contains examples of custom aliases
ll
- just ls -l
cls
- clears the terminal windowps1
- sets the command prompt textAdded more 'die-fast' error handling into the building and publishing scripts. They exit immediately if the image building or pushing commands fail.
Main changes:
env.rc
, push
and post_push
have been updatedreadme-local-building-example.md
got a new section Tips and examples
, containing
How to deploy all images into one repository
ci-builder.sh
help modeThis release brings updated and significantly shortened README files, because most of the content has been moved into the new User guide.
This release introduces a new feature FEATURES_OVERRIDING_ENVV
, which controls the overriding or adding of environment variables at the container startup-time.
Meaning, after the container has already been created.
The feature is enabled by default.
It can be disabled by setting the variable FEATURES_OVERRIDING_ENVV
to zero when the container is created or the image is built.
Be aware that any other value than zero, even if unset or empty, enables the feature.
If FEATURES_OVERRIDING_ENVV=1
, then the container startup script will look for the file $HOME/.override/.override_envv.rc
and source all the lines that begin with the string 'export ' at the first position and contain the '=' character.
The overriding file can be provided from outside the container using bind mounts or volumes.
The lines that have been actually sourced can be reported into the container's log if the startup parameter --verbose
or --debug
is provided.
This feature is an enhanced implementation of the previously available functionality known as Overriding VNC/noVNC parameters at the container startup-time.
Therefore this is a breaking change for the users that already use the VNC/noVNC overriding.
They need to move the content from the previous file $HOME"/.vnc_override.rc
into the new file $HOME/.override/.override_envv.rc
.
This release mitigates the problems with the edge use case, when users bind the whole $HOME
directory to an external folder on the host computer.
Please note that I recommend to avoid doing that. If you really want to, then your best bet is using the Docker volumes. That is the only option I've found, which works across the environments. In the discussion thread #39 I've described the way, how to initialize a bound $HOME
folder, if you really want to give it a try.
Main changes:
.initial_sudo_password
has been moved from the $HOME
to the $STARTUPDIR
folder.initial_sudo_password
is not deleted, but cleared after the container user is created