Thanks for the feedback. If you could share which Dockerfile you use and how you use it, I’d appreciate that. I’d like to not disrupt people if I make a change or at least collaborate on the features that should be preserved.
I’m leaning toward introducing a new separate Dockerfile first and then maybe deprecating and removing the old unused ones over time. On Wednesday, November 17, 2021, Sina Kashipazha <s.kashipa...@protonmail.com.invalid> wrote: > Hey Marcus, > > We use docker to build cloudstack packages when we want to build > cloudstack for the different target OS. That is our only use case, which > happens once in a blue moon :) > > Kind regards, > Sina > > ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ > > On Tuesday, November 16th, 2021 at 22:30, Marcus <shadow...@gmail.com> > wrote: > > > I take the silence to perhaps mean that nobody is actively using the > Docker > > > > image tooling, but maybe the conference was just too much of a > distraction > > > > last week :-) > > > > Mainly I'm just wondering if I should be trying to improve the old stuff, > > > > or leaving it be and adding a new Dockerfile. The marvin bit is > secondary. > > > > On Tue, Nov 9, 2021 at 10:15 AM Marcus shadow...@gmail.com wrote: > > > > > Hi all, I've been familiarizing myself with the Docker image tooling in > > > > > > CloudStack, and I have a few questions. I've been playing with a > > > > > > multi-stage build that shrinks the image from ~4Gi to ~800Mi, packages > just > > > > > > the jar, some UI, and a JDK thinking that it might be more usable. > > > > > > 1. Is there anyone actively using these Dockerfiles? It might be > > > > > > interesting to know what workflows they're a part of and whether > they can > > > > > > be changed or if new files should be created. > > > > > > 2. I see the Dockerfile.marvin points to a 'builds.cloudstack.org' to > > > > > > pull a Marvin bundle, which seems to be down. Do these artifacts > need to > > > > > > be moved to 'download.cloudstack.org' or is this just a temporary > > > > > > outage, or is it only reachable from CI? I do see the 'latest' tag > > > > > > pulls (which is three years old). > > >
