Hi Flavio, On Tue, 2017-06-20 at 15:40 +0200, Flavio Junqueira wrote:
Hey Francesco, Thanks for putting this together. I have a couple of comments from our side: - I'm not sure whether this is an issue for others, and would actually be interested in hearing whether it is or not, but the use of Alpine is a deal breaker for us because of the GPL lawsuit stories around busybox. I didn't know about the GPL lawsuit and I don't even know about the possibile implications. One possibility is to create an alternate build based on debian or centos and keep alpine one with labels x.x.x-alpine (e.g 4.4.0-alpine) like many projects do. I am curious about the community's views about this matter. - Will we be setting parameters via environment variables? Via enviornment variables and via direct configuration files mounted on the container. See https://github.com/caiok/bookkeeper-docker#configuration -Flavio On 20 Jun 2017, at 14:09, Francesco Caliumi - Diennea <francesco.cali...@diennea.com<mailto:francesco.cali...@diennea.com>> wrote: I wrote the first draft of the proposal: https://cwiki.apache.org/confluence/display/BOOKKEEPER/BP-10+-+Official+Bookkeeper+Docker+Image <https://cwiki.apache.org/confluence/display/BOOKKEEPER/BP-10+-+Official+Bookkeeper+Docker+Image> Any suggestion would be appreciated. On Thu, 2017-06-01 at 12:56 +0000, Francesco Caliumi - Diennea wrote: Thanks Sijie, I will re-read docker hub guidelines and write the proposal accordingly. Alas, I had no time for refreshing the topic, so I think that discussing it is useless in today meeting, but I think that in the next one I will be ready. On Wed, 2017-05-31 at 13:12 -0700, Sijie Guo wrote: Francesco, I granted you the permission for confluence page. I am okay with putting the docker build files in the main repo and configuring the jenkins build to automatically push the docker images to docker hub for snapshots. - Sijie On Wed, May 31, 2017 at 12:07 AM, Francesco Caliumi - Diennea < francesco.cali...@diennea.com<mailto:francesco.cali...@diennea.com> <mailto:francesco.cali...@diennea.com><mailto:francesco.cali...@diennea.com <mailto:francesco.cali...@diennea.com>><mailto:francesco.cali...@diennea.com <mailto:francesco.cali...@diennea.com>>> wrote: Hi Sijie, the issue is https://issues.apache.org/ <https://issues.apache.org/> jira/browse/BOOKKEEPER-974. There is also a meeting note ( https://cwiki.apache.org/confluence/display/BOOKKEEPER/ <https://cwiki.apache.org/confluence/display/BOOKKEEPER/> 2017-2-10+Meeting+notes) that introduced the need to choose between keeping docker build files in a seperate repo (like zookkeeper does) or put them in bookkeeper main repo. I need to refresh my mind on the matter anyway, I'll try to do it before next meeting. My user on confluence is "caio". Francesco. On Tue, 2017-05-30 at 10:48 -0700, Sijie Guo wrote: Ah, sorry my bad. Do you mind pointing me the JIRA/pull request that needs responses from me? What is your confluence wiki handle? I can grant you the edit permission. - Sijie On Mon, May 29, 2017 at 12:44 AM, Francesco Caliumi - Diennea < francesco.cali...@diennea.com<mailto:francesco.cali...@diennea.com> <mailto:francesco.cali...@diennea.com><mailto:francesco.cali...@diennea.com <mailto:francesco.cali...@diennea.com>><mailto:francesco.cali...@diennea.com <mailto:francesco.cali...@diennea.com>><mailto:francesco.cali...@diennea.com <mailto:francesco.cali...@diennea.com>>> wrote: Hi all, some months ago I wrote a prototype of a docker image that follows the standard rules of official docker images. The work was suspended waiting for some responses from Sijie, but I think it would be easier to follow the thread if it is tied to a bookkeeper proposal on Confluence. @Sijie: could you give me edit access to confluence in order to write down the state of the work and the open points that need a decision from the community? Thanks, Francesco. -- Francesco Caliumi Developer @ Diennea - MagNews Tel.: (+39) 0546 066100 - Int. 266 Viale G.Marconi 30/14 - 48018 Faenza (RA) [Magnews.it]<http://www.magnews.it/it> [Linkedin]<http://www.linkedin.com/company/diennea---magnews> [Twitter] <http://twitter.com/DienneaMagNews> [Facebook] < http://www.facebook.com/pages/MagNews/197617841797> [Newsletter] < http://www.magnews.it/it/iscriviti-alla-newsletter> ________________________________ Iscriviti alla nostra newsletter per rimanere aggiornato su digital ed email marketing! http://www.magnews.it/newsletter/ The information in this email is confidential and may be legally privileged. If you are not the intended recipient please notify the sender immediately and destroy this email. Any unauthorized, direct or indirect, disclosure, copying, storage, distribution or other use is strictly forbidden. -- Francesco Caliumi Developer @ Diennea - MagNews Tel.: (+39) 0546 066100 - Int. 266 Viale G.Marconi 30/14 - 48018 Faenza (RA) [Magnews.it]<http://www.magnews.it/it> [Linkedin]<http://www.linkedin.com/company/diennea---magnews> [Twitter] <http://twitter.com/DienneaMagNews> [Facebook] < http://www.facebook.com/pages/MagNews/197617841797> [Newsletter] < http://www.magnews.it/it/iscriviti-alla-newsletter> ________________________________ Iscriviti alla nostra newsletter per rimanere aggiornato su digital ed email marketing! http://www.magnews.it/newsletter/ The information in this email is confidential and may be legally privileged. If you are not the intended recipient please notify the sender immediately and destroy this email. Any unauthorized, direct or indirect, disclosure, copying, storage, distribution or other use is strictly forbidden. -- Francesco Caliumi Developer @ Diennea - MagNews Tel.: (+39) 0546 066100 - Int. 266 Viale G.Marconi 30/14 - 48018 Faenza (RA) [Magnews.it]<http://www.magnews.it/it> [Linkedin]<http://www.linkedin.com/company/diennea---magnews> [Twitter] <http://twitter.com/DienneaMagNews> [Facebook] <http://www.facebook.com/pages/MagNews/197617841797> [Newsletter] <http://www.magnews.it/it/iscriviti-alla-newsletter> ________________________________ Iscriviti alla nostra newsletter per rimanere aggiornato su digital ed email marketing! http://www.magnews.it/newsletter/ The information in this email is confidential and may be legally privileged. If you are not the intended recipient please notify the sender immediately and destroy this email. Any unauthorized, direct or indirect, disclosure, copying, storage, distribution or other use is strictly forbidden. -- Francesco Caliumi Developer @ Diennea - MagNews Tel.: (+39) 0546 066100 - Int. 266 Viale G.Marconi 30/14 - 48018 Faenza (RA) [Magnews.it <http://magnews.it/>]<http://www.magnews.it/it <http://www.magnews.it/it>> [Linkedin]<http://www.linkedin.com/company/diennea---magnews <http://www.linkedin.com/company/diennea---magnews>> [Twitter] <http://twitter.com/DienneaMagNews <http://twitter.com/DienneaMagNews>> [Facebook] <http://www.facebook.com/pages/MagNews/197617841797 <http://www.facebook.com/pages/MagNews/197617841797>> [Newsletter] <http://www.magnews.it/it/iscriviti-alla-newsletter <http://www.magnews.it/it/iscriviti-alla-newsletter>> ________________________________ Iscriviti alla nostra newsletter per rimanere aggiornato su digital ed email marketing! http://www.magnews.it/newsletter/ <http://www.magnews.it/newsletter/> The information in this email is confidential and may be legally privileged. If you are not the intended recipient please notify the sender immediately and destroy this email. Any unauthorized, direct or indirect, disclosure, copying, storage, distribution or other use is strictly forbidden. -- Francesco Caliumi Developer @ Diennea - MagNews Tel.: (+39) 0546 066100 - Int. 266 Viale G.Marconi 30/14 - 48018 Faenza (RA) [Magnews.it]<http://www.magnews.it/it> [Linkedin]<http://www.linkedin.com/company/diennea---magnews> [Twitter] <http://twitter.com/DienneaMagNews> [Facebook] <http://www.facebook.com/pages/MagNews/197617841797> [Newsletter] <http://www.magnews.it/it/iscriviti-alla-newsletter> ________________________________ Iscriviti alla nostra newsletter per rimanere aggiornato su digital ed email marketing! http://www.magnews.it/newsletter/ The information in this email is confidential and may be legally privileged. If you are not the intended recipient please notify the sender immediately and destroy this email. Any unauthorized, direct or indirect, disclosure, copying, storage, distribution or other use is strictly forbidden.
