Hi,
thanks a lot for the thorough responses, this makes it much clearer!
Then I think in order to avoid this happening again we'll go for it
mirror at least the latest release.
Best Regards,
Dominick
On 01.10.21 15:52, Christofer Dutz wrote:
Hi Dominick,
yeah … as I said, this is less a technical than a legal issue.
The StreamPipes project, as an Apache project has to ensure the correctness of
code it releases. That’s why an Apache release is quite a process. But this
ensures the safety of users using our products and it helps enforce the legal
shield the ASF protects it’s contributors with. We have to ensure this shield
is not harmed. This could be harmed, if we were starting to relese artifacts
with legal issues.
We have the concept of convenience binaries, but distributing them is a bit
tricky. In Maven this is no issue, as the SNAPSHOT handling is built into the
build system. With Docker and other forms of distribution, this usually isn’t
the case. So we have be careful as to what is considered a release, a
convenience binary and a snapshot which should generally only be used for
experimenting and development.
If Streampipes now decided to start deploying docker images to something
„StreamPipeHub“. This would be considered problematic as it could imply being
the official distribution channel, which it is not. Also would the usage of
normal versions for doing so sort of imply something has went through the
process of a release, which it clearly is not.
I hope this explains things a bit better ;-)
And a big +1 to Dominiks explanation … this is how you could solve this problem
for yoursef … just be sure to never announce or promote this as any official
release channel.
Chris
-----Ursprüngliche Nachricht-----
Von: Dominik Riemer <[email protected]>
Gesendet: Freitag, 1. Oktober 2021 11:41
An: [email protected]
Betreff: Re: Alternative Docker Registry
Hi Dominick,
just to clarify on Chris' response:
Your are absolutely free to set up your own private Docker registry and build/push
StreamPipes images there. It would only be an issue if someone would distribute
"official" StreamPipes images somewhere using the Apache StreamPipes brand,
which is not the case.
For you as a user, the Apache License gives you all rights to build Docker
images from our source code and push it to your private registry. One approach
would be that you setup your internal CI system to pull our source code
regularly and build/deploy them to your internal registry. You could also
create a Github workflow and publish the images to your own Github packages
registry.
You can find all Docker images to do that in the repos (e.g.,
streampipes-backend, ui and in the extensions project) and also the currently
used Github Actions workflows might help.
Hope this helps!
Dominik
On 2021/10/01 08:18:32, Dominick Madden <[email protected]> wrote:
Hi,
thanks for the response! I am logged in to the Docker Hub locally on
my machine, so creating a minikube instance wouldn't be a problem. Our
production k8s infrastructure apparently does not operate with a
Docker Hub account though. Even after the wait since yesterday the
limit is still in effect. I just created an issue and the matching PR.
@Christopher:
I don't really see an issue with uploading publicly available Docker
images to your own registry, but also I'm no lawyer, so who knows. I
think there even are (incomplete) mirrors of the Docker Hub around the
web. But again, legally I'm not 100% sure. Thanks for the input!
On 30.09.21 16:57, Philipp Zehnder wrote:
Hi Dominick,
sorry I do not have a private registry with all the StreamPipes images.
However, I never had any issues with docker hub so far. Are you logged in to
docker hub?
I think the pull policy can be changed. Especially for the release versions, I
do not think that it is necessary to always pull the image.
So if you like you are welcome to make a pull request, or does anyone else see
a problem with this change?
Philipp
On 30. Sep 2021, at 13:31, Dominick Madden<[email protected]> wrote:
Hi StreamPipes devs,
I was wondering if somebody has set up a private Docker registry somewhere to
avoid using the Docker Hub. And if so, if they could share. After multiple
setups due to debugging and testing we have run into Docker Hub's rate limit.
Also on that note I'd suggest to change the default imagePullPolicy of the helm
chart to IfNotPresent to avoid this problem altogether. Or maybe have it be
configurable. What do you think?
Best regards,
Dominick
--
EDI GmbH
Engineering Data Intelligence
Hermann-Weick-Weg 3
76229 Karlsruhe (Grötzingen), Deutschland
Dominick Madden
Senior Backend Developer
Telefon: +49 721 79199 155
Email:[email protected] <mailto:[email protected]>
WWW:
www<http://www.edi.gmbh/en/>.<http://www.edi.gmbh/en/>edi.gmbh<http://www.edi.gmbh/en/>
<https://www.youtube.com/channel/UCaLsW2mgWB3BB8isicyqU6g?view_as=subscriber><linkedin_40x40.png><https://www.linkedin.com/authwall?trk=ripf&trkInfo=AQEzpm6QRZtfBwAAAXaG-GNQu9A0kNpT5EDSPJWHJJdrGfQWIQkO6aw4SCy1fkWaYk9JsvuRCRdMHe30l4tZpPkDAKWlnjiA1OIvsvMogKwGpP4h36ZJBkNfWRakUrXQi_ES-Ig=&originalReferer=&sessionRedirect=https%3A%2F%2Fwww.linkedin.com%2Fcompany%2Fengineering-data-intelligence>
<youtube.png><https://www.youtube.com/channel/UCaLsW2mgWB3BB8isicyqU6g>
<digitalisation.png> <100 orte.png> <OPC.png>
Die EDI GmbH wird vertreten durch die Geschäftsführer Dr.-Ing. Mohanad El-Haji
und Dr.-Ing. Thomas Freudenmann.
Sitz der Gesellschaft ist Karlsruhe, HRB 723936 (Registergericht AG
Mannheim)
<http://www.edi.gmbh/en/>
--
*EDI GmbH*
/Engineering Data Intelligence/
Hermann-Weick-Weg 3
76229 Karlsruhe (Grötzingen), Deutschland
Dominick Madden
Senior Backend Developer
Telefon: +49 721 79199 155
Email: [email protected]
WWW: www <http://www.edi.gmbh/en/>. <http://www.edi.gmbh/en/>edi.gmbh
<http://www.edi.gmbh/en/>
<https://www.youtube.com/channel/UCaLsW2mgWB3BB8isicyqU6g?view_as=subs
criber>linkdein
<https://www.linkedin.com/authwall?trk=ripf&trkInfo=AQEzpm6QRZtfBwAAAX
aG-GNQu9A0kNpT5EDSPJWHJJdrGfQWIQkO6aw4SCy1fkWaYk9JsvuRCRdMHe30l4tZpPkD
AKWlnjiA1OIvsvMogKwGpP4h36ZJBkNfWRakUrXQi_ES-Ig=&originalReferer=&sess
ionRedirect=https%3A%2F%2Fwww.linkedin.com%2Fcompany%2Fengineering-dat
a-intelligence> youtube
<https://www.youtube.com/channel/UCaLsW2mgWB3BB8isicyqU6g>
digitalisation 100 orte opc
Die EDI GmbH wird vertreten durchdie Geschäftsführer Dr.-Ing.
MohanadEl-Haji und Dr.-Ing. ThomasFreudenmann.
Sitz der Gesellschaft ist Karlsruhe,HRB 723936 (Registergericht
AGMannheim)
<http://www.edi.gmbh/en/>
--
*EDI GmbH*
/Engineering Data Intelligence/
Hermann-Weick-Weg 3
76229 Karlsruhe (Grötzingen), Deutschland
Dominick Madden
Senior Backend Developer
Telefon: +49 721 79199 155
Email: [email protected]
WWW: www <http://www.edi.gmbh/en/>. <http://www.edi.gmbh/en/>edi.gmbh
<http://www.edi.gmbh/en/>
<https://www.youtube.com/channel/UCaLsW2mgWB3BB8isicyqU6g?view_as=subscriber>linkdein
<https://www.linkedin.com/authwall?trk=ripf&trkInfo=AQEzpm6QRZtfBwAAAXaG-GNQu9A0kNpT5EDSPJWHJJdrGfQWIQkO6aw4SCy1fkWaYk9JsvuRCRdMHe30l4tZpPkDAKWlnjiA1OIvsvMogKwGpP4h36ZJBkNfWRakUrXQi_ES-Ig=&originalReferer=&sessionRedirect=https%3A%2F%2Fwww.linkedin.com%2Fcompany%2Fengineering-data-intelligence>
youtube <https://www.youtube.com/channel/UCaLsW2mgWB3BB8isicyqU6g>
digitalisation 100 orte opc
Die EDI GmbH wird vertreten durchdie Geschäftsführer Dr.-Ing.
MohanadEl-Haji und Dr.-Ing. ThomasFreudenmann.
Sitz der Gesellschaft ist Karlsruhe,HRB 723936 (Registergericht AGMannheim)
<http://www.edi.gmbh/en/>
