From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753107AbcHVIIM (ORCPT ); Mon, 22 Aug 2016 04:08:12 -0400 Received: from mail-lf0-f66.google.com ([209.85.215.66]:33816 "EHLO mail-lf0-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751704AbcHVIIH (ORCPT ); Mon, 22 Aug 2016 04:08:07 -0400 From: Dmitry Monakhov To: "Theodore Ts'o" Cc: linux-kernel@vger.kernel.org Subject: Re: [PATCH 6/6] Add dockerfile In-Reply-To: <20160821153547.3shrny7phed22xew@thunk.org> References: <1471553651-9547-1-git-send-email-dmonakhov@openvz.org> <1471553651-9547-7-git-send-email-dmonakhov@openvz.org> <20160819052106.GC10888@thunk.org> <87eg5l6rcg.fsf@openvz.org> <20160819232953.GB12834@thunk.org> <87lgzrptgx.fsf@openvz.org> <20160820194530.GA9693@thunk.org> <87y43ql481.fsf@openvz.org> <20160821153547.3shrny7phed22xew@thunk.org> User-Agent: Notmuch/0.18.1 (http://notmuchmail.org) Emacs/24.4.1 (x86_64-pc-linux-gnu) Date: Mon, 22 Aug 2016 11:07:59 +0300 Message-ID: <87y43p9qg0.fsf@openvz.org> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --=-=-= Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Theodore Ts'o writes: > On Sun, Aug 21, 2016 at 03:02:38PM +0300, Dmitry Monakhov wrote: >> Probably it it reasonable to create dedicated directory ./docker >> and place all docker related crap there: >> # build scripts >> docker/Dockerfile.build-env >> docker/Dockerfile.run-env >> # And some run scripts >> # Build all environment from scratch >> docker/docker-build.sh >> # Move config, kernel, root_fs.img inside container and run {gce,kvm}-xf= stests.sh >> docker/docker-kvm-xfstests.sh=20 >> docker/docker-gce-xfstests.sh > > I thought about that, but my current thinking is to have one > Dockerfile which is in the top-level directory, and one which is in > the kvm-xfstests directory. > > I've already created a tytso/xfststs-bld Docker image which was > generated using: > > docker build -t tytso/xfstests-bld https://github.com/tytso/xfstests-bld.= git Nice. Now image is no longer generated by Russian hacker. Hitler finally can sleep well :) > > By putting the Dockerfile in the top-level directory, I can use the > command "COPY . /devel/xfstests-bld" in the Dockerfile, and so we can > get a clean build build that way. Yes. That is reasonable. I do not know that build context can emerge from U= RL. > > By putting a Dockerfile in the kvm-xfstests directory, then all I have > to do is to put a "COPY . /usr/local/lib/kvm-xfstests" which will copy > all of the kvm-xfstests directory directly where we want the files in > the kvm-xfstests Docker image. I'm assuming that my release process > will first build root_fs.i386 and root_fs.x86_64 using debian chroots, > and then upload them to www.kernel.org. I'll then run: > > docker build -t tytso/kvm-xfstests https://github.com/tytso/xfstests-bld.= git:kvm-xfstests Cool. The only minor comment is that command should be: docker build -t tytso/kvm-xfstests -f kvm-xfstests/Dockerfile https://githu= b.com/tytso/xfstests-bld.git:kvm-xfstests > > ... and then the Dockerfile will pull the root_fs.i386 from > ftp.kernel.org. > > What do you think? > > - Ted --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCgAGBQJXurLgAAoJELhyPTmIL6kBVEEH/1J4HadJSmGr+c1AL6AAosH/ kkv1/MPrIkYipYhw0VWImDhMDA/4Alkjfahr9AfhVQ2+UcBQRQqBV6pnRdNBdldi 1SIG/hWrNEWkGeqoE3l9unH8QA8nGDncBEPNpDH8afQ8SQU7Yl20Vv+EdmltdicL Xk75TxtKGRMaStTpi+c2TRgQC96nomr+7BWuyBwhyzI5Zw2qiZUmQfhfV3iU1PoQ C8i3cpn9Y73R2zx1D2CaaBSFKuut/EtDw/2BBcL4d6Hox9UVsIhc4h0b4PsUocDp 1EOC197yuY/UsW6NCcguwNoboX5nm/5rx8sRdoHSE8RHWfCioEaLF3guQUN6fy4= =wh07 -----END PGP SIGNATURE----- --=-=-=--