Re: [PATCH 2/2 -perfbook] FAQ-BUILD: Add Q&A on Docker image

["Paul E. McKenney" <paulmck@kernel.org>]

On Wed, Jan 06, 2021 at 11:36:14PM +0900, Akira Yokosawa wrote:
> On Wed, 6 Jan 2021 19:32:42 +0900, Akira Yokosawa wrote:
> > From 165d967a252652e2ef5af82ce62536dbcf314600 Mon Sep 17 00:00:00 2001
> > From: Akira Yokosawa <akiyks@gmail.com>
> > Date: Wed, 6 Jan 2021 19:03:55 +0900
> > Subject: [PATCH 2/2 -perfbook] FAQ-BUILD: Add Q&A on Docker image
> > 
> > The template Dockerfile and the usage explained is a tutorial level.
> > Suggestions from Docker-savvy people are more than welcome.
> > 
> > Signed-off-by: Akira Yokosawa <akiyks@gmail.com>
> > ---
> >  FAQ-BUILD.txt | 22 ++++++++++++++++++++++
> >  1 file changed, 22 insertions(+)
> > 
> > diff --git a/FAQ-BUILD.txt b/FAQ-BUILD.txt
> > index 2eeb9fbb..d4c18424 100644
> > --- a/FAQ-BUILD.txt
> > +++ b/FAQ-BUILD.txt
> > @@ -273,3 +273,25 @@
> >  
> >  		    sudo updmap-sys --syncwithtrees --force
> >  		    sudo updmap-sys
> > +
> > +14.	I want a stable environment to build perfbook.pdf.
> > +	Isn't some container image available in that regard?
> > +
> > +	A.	You can find a template Dockerfile under the docker/
> > +		subdirectory.
> > +		A docker image built from it can be pulled by:
> > +
> > +		    docker pull akiyks/perfbook-build-env:focal
> > +
> > +		It can be run with the command:
> > +
> > +		    docker run --rm -it -v <path to perfbook dir>:/work \
> > +		      akiyks/perfbook-build-env:focal bash
> 
> If we add a "-u" option specifying host-side uid:gid to run the container,
> it is safe to do Git operations from inside the container.
> This is because the container does all the I/O to the mounted host directory.
> So the following note can be removed.
> 
> I'll respin 2/2.

This does look like it would be very helpful to people trying to get
their environment set up!

							Thanx, Paul

>         Thanks, Akira
> 
> > +
> > +		Note:
> > +		    The directory to be mounted to /work you give to the
> > +		    "-v" option should be a newly cloned git repository.
> > +		    You should avoid using any git command from the container
> > +		    that might modify repository meta data and change their
> > +		    owner.
> > +		    Git operations should be done from the host side.
> >