For version format x.y.z, three tags as below
tag: x.y.z
tag1: x.y
tag2: x
They all point to the latest image.
Once app got updated (minor updates, z to z1), the tag x.y.z
will be replaced by x.y.z1, but the tag x or x.y may still
keep.
Signed-off-by: Qi Zheng <qi.zheng@intel.com>
and nginx, postgres, ...
Two tags are to be added for each containers.
1. exact app version tag, usually format as x.y.z.
For example, 5.0.6 for redis.
2. major app version tag, usually format as x.
For example, 5 for redis.
For some special cases, the major format as x.y.
For example, 1.17 for nginx, 3.7 for python.
Signed-off-by: Qi Zheng <qi.zheng@intel.com>
When removing the duplicated file and directory via rm -d,
if it's a non-empty directory, it will prompt the warning
message that the directory could not be removed becuase it
is not empty. This is as expectation, as there are other
files under the same diretory and we need to keep them.
Hide these warning message to avoid confusion.
Signed-off-by: Liu, Jianjun <jianjun.liu@intel.com>
Convert golang, node, openjdk, perl, php, python,
rabbitmq, ruby and tensorflow containers to be based
on the minimal os-core container, using a multistage
build technique to add additional Clear Linux content.
Signed-off-by: Liu, Jianjun <jianjun.liu@intel.com>
To help analyze the container image size by layers, assume
each container image be comprised of:
Layer 1: clearlinux:latest
Layer 2: swupd update
Other layers: the container configurations
With this, we can continue to optimize layer size accordingly.
Signed-off-by: Qi Zheng <qi.zheng@intel.com>
