This repository is for -base and -builder containers for building derivative containers (such as poky-container) for containerized Yocto Project builds.
GNU General Public License v2.0
145
stars
57
forks
source link
headless / cli only image toggle (remove tightvnc) #65
I recently had a group discussion about using CROPS, and somebody mentioned that for our use case of a build server, the built in VNC server would be undesirable from a bloat / security perspective.
It is my understanding this service wont run by default, so an unauthorized user or code would be required to invoke it anyways. However, you can't really argue that its unnecessary bloat for this use case.
So I started to wonder that perhaps there should be a toggle to include or exclude it. On a local PC the VNC could be a useful to the development workflow. However for a build server, it wouldn't necessarily need it.
So just wanted to capture this idea, and see if anybody wanted to discuss perhaps providing a better user story in this case.
I recently had a group discussion about using CROPS, and somebody mentioned that for our use case of a build server, the built in VNC server would be undesirable from a bloat / security perspective. It is my understanding this service wont run by default, so an unauthorized user or code would be required to invoke it anyways. However, you can't really argue that its unnecessary bloat for this use case.
So I started to wonder that perhaps there should be a toggle to include or exclude it. On a local PC the VNC could be a useful to the development workflow. However for a build server, it wouldn't necessarily need it.
So just wanted to capture this idea, and see if anybody wanted to discuss perhaps providing a better user story in this case.
Thanks