All of lore.kernel.org
 help / color / mirror / Atom feed
From: Akira Yokosawa <akiyks@gmail.com>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: perfbook@vger.kernel.org, Akira Yokosawa <akiyks@gmail.com>
Subject: Re: [PATCH v2 0/2 -perfbook] Add Dockerfile and Q&A
Date: Fri, 8 Jan 2021 07:44:14 +0900	[thread overview]
Message-ID: <2358d87c-302a-1e75-60b7-43ded524e447@gmail.com> (raw)
In-Reply-To: <20210107175446.GN2743@paulmck-ThinkPad-P72>

On Thu, 7 Jan 2021 09:54:46 -0800, Paul E. McKenney wrote:
> On Thu, Jan 07, 2021 at 10:49:08PM +0900, Akira Yokosawa wrote:
>> Hi,
>>
>> This is the v2 of the patch set.
>>
>> The strange -nq build Paul thought he had encountered prompted me
>> to prepare a Docker image for stable build environment.
>> Such an environment can be helpful as a contingency plan when
>> some package's update causes breakage in perfbook's build scripts,
>> such as the build error recently reported by Dmitry and Felipe.
>>
>> This patch set adds a Dockerfile I used and a Q&A entry in
>> FAQ-BUILD.txt.
>> docker/ subdirectory also holds steel city comic font to be copied
>> to the image.
>>
>> Changes v1 -> v2:
>>   o Add a few ARG commands in Dockerfile for custimizable uid and gid.
>>   o Entry #14 in FAQ-BUILD.txt recommends the use of -u option to
>>     use uid:gid of host side.
>>   o Changed dockerhub repository name to perfbook-build-focal.
>>   o Reference #14 from #5 in FAQ-BUILD.text
>>
>>         Thanks, Akira
> 
> Applied and pushed, thank you!  I did the usual wordsmithing, so please
> let me know if I messed anything up.

Thank you!  Now it looks perfect.

> 
> Showing my ignorance of Docker...
> 
> My guess from reading the FAQ is that the new docker/Dockerfile is
> used to build a new docker image, and that it is not needed by those
> using your akiyks/perfbook-build-focal:latest.  Is my guess correct?

You guessed quite right.
One advantage of docker is that once you pulled my container image,
large layers installing various packages are used unmodified in a
new build.
Building a image with an alternative <uid:gid> pair will take just a
few seconds.
Initial pull of the image can take several minutes or longer depending
on the network bandwidth.

For instructions to install Docker Engine on Ubuntu, see:
https://docs.docker.com/engine/install/ubuntu/.

The command in the FAQ assumes your user id belong to the "docker"
group. Otherwise, every docker command needs "sudo".

One thing you need to care is the disk capacity under /var/lib/docker.

If you are behind a corporate proxy, you need to setup proxy for docker
service. See: https://docs.docker.com/network/proxy/

        Thanks, Akira

> 
> 						Thanx, Paul
> 
>> --
>> Akira Yokosawa (2):
>>   Add files to build Docker image for perfbook build
>>   FAQ-BUILD: Add Q&A on Docker image
>>
>>  FAQ-BUILD.txt                       |  38 +++++++++++++++++++++++++---
>>  docker/Dockerfile                   |  21 +++++++++++++++
>>  docker/steel-city-comic.regular.ttf | Bin 0 -> 23280 bytes
>>  3 files changed, 56 insertions(+), 3 deletions(-)
>>  create mode 100644 docker/Dockerfile
>>  create mode 100644 docker/steel-city-comic.regular.ttf
>>
>> -- 
>> 2.17.1
>>
>>

      reply	other threads:[~2021-01-07 22:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-06 10:28 [PATCH 0/2 -perfbook] Add Dockerfile and Q&A Akira Yokosawa
2021-01-06 10:31 ` [PATCH 1/2 -perfbook] Add files to build Docker image for perfbook build Akira Yokosawa
2021-01-06 10:32 ` [PATCH 2/2 -perfbook] FAQ-BUILD: Add Q&A on Docker image Akira Yokosawa
2021-01-06 14:36   ` Akira Yokosawa
2021-01-06 23:29     ` Paul E. McKenney
2021-01-07 13:49 ` [PATCH v2 0/2 -perfbook] Add Dockerfile and Q&A Akira Yokosawa
2021-01-07 13:51   ` [PATCH v2 1/2 -perfbook] Add files to build Docker image for perfbook build Akira Yokosawa
2021-01-07 13:52   ` [PATCH v2 2/2 -perfbook] FAQ-BUILD: Add Q&A on Docker image Akira Yokosawa
2021-01-07 17:54   ` [PATCH v2 0/2 -perfbook] Add Dockerfile and Q&A Paul E. McKenney
2021-01-07 22:44     ` Akira Yokosawa [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2358d87c-302a-1e75-60b7-43ded524e447@gmail.com \
    --to=akiyks@gmail.com \
    --cc=paulmck@kernel.org \
    --cc=perfbook@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.