From dev-return-86251-archive-asf-public=cust-asf.ponee.io@sling.apache.org Wed Jan 31 16:03:19 2018 Return-Path: X-Original-To: archive-asf-public@eu.ponee.io Delivered-To: archive-asf-public@eu.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by mx-eu-01.ponee.io (Postfix) with ESMTP id 163F2180662 for ; Wed, 31 Jan 2018 16:03:19 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 0606B160C35; Wed, 31 Jan 2018 15:03:19 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 466CC160C25 for ; Wed, 31 Jan 2018 16:03:18 +0100 (CET) Received: (qmail 45878 invoked by uid 500); 31 Jan 2018 15:03:17 -0000 Mailing-List: contact dev-help@sling.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@sling.apache.org Delivered-To: mailing list dev@sling.apache.org Received: (qmail 45867 invoked by uid 99); 31 Jan 2018 15:03:17 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 31 Jan 2018 15:03:17 +0000 Received: from [10.136.162.86] (unknown [193.105.140.131]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id 6F84F1A00D0 for ; Wed, 31 Jan 2018 15:03:14 +0000 (UTC) Message-ID: <1517410990.2420.12.camel@apache.org> Subject: Sling docker image From: Robert Munteanu To: dev@sling.apache.org Date: Wed, 31 Jan 2018 17:03:10 +0200 Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.26.4 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Hi, Related to the ongoing github.com/apache/sling landing page discussion, I'd like to discuss our docker setup. Currently we provide an apachelsling/sling [1] image, which is OK. I investigated setting up a build under the more official apache account, but unfortunately the automated docker builds picks up the image name from the repository, so we ended up with apache/sling-org-apache-sling- starter-docker, which is quite ugly. If we choose automated builds, getting back the 'sling' repository is something we should consider. Thanks, Robert [1]: https://hub.docker.com/r/apachesling/sling/ [2]: https://hub.docker.com/r/apache/sling-org-apache-sling-starter-doc ker/