Proposal: Make a common base image
Background
There are many component images in Cyclone, cyclone-server, cyclone-workflow-controller, cyclone-workflow-coordinator, etc. They use a different base image, such as alpine:3.8 ubuntu:18.10 and bash:4.1.17, and almost every image built needs to connect to the network, installing subversion, installing docker and so on.
Disadvantages of that:
- we can not build even one Cyclone image in a no network environment
- we must do some duplicated works, like downloading subversion, in some images building.
Proposal
I think we can:
Advantages
Could resolve problems described in the background
Disavantages
Some images may container some tools they don't need and make their size bigger than before. But I think that is acceptable.
/cc @supereagle @hyy0322 @bbbmj
Uncomment only one, leave it on its own line:
/kind proposal
What happened:
What you expected to happen:
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Proposal: Make a common base image
Background
There are many component images in Cyclone,
cyclone-server,cyclone-workflow-controller,cyclone-workflow-coordinator, etc. They use a different base image, such asalpine:3.8ubuntu:18.10andbash:4.1.17, and almost every image built needs to connect to the network, installing subversion, installing docker and so on.Disadvantages of that:
Proposal
I think we can:
alpine:3.8ubuntu:18.10andbash:4.1.17toalpine:3.8.(almostly done except for sonarqube)alpine:3.8and installed all tools from the internet for other component images. Naming the common base image is difficult for me, how aboutcyclone-base?Advantages
Could resolve problems described in the background
Disavantages
Some images may container some tools they don't need and make their size bigger than before. But I think that is acceptable.
/cc @supereagle @hyy0322 @bbbmj
What happened:
What you expected to happen:
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?: