Bug 1755670 - Source/Docker strategy builds generate warning: pkg/chroot: error unmounting
Summary: Source/Docker strategy builds generate warning: pkg/chroot: error unmounting
Keywords:
Status: CLOSED DUPLICATE of bug 1772179
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Build
Version: 4.1.z
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: 4.3.0
Assignee: Nalin Dahyabhai
QA Contact: wewang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-09-26 02:07 UTC by Masatoshi Hayashi
Modified: 2023-10-20 14:59 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-01-22 15:42:39 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Masatoshi Hayashi 2019-09-26 02:07:57 UTC
Description of problem:

When a user runs builds on OpenShift, the warning message is generated:

~~~
$ oc logs build/samplebuild

...
STEP 5: COPY upload/src /tmp/src
STEP 6: RUN chown -R 185:0 /tmp/src
time="2019-09-26T01:27:02Z" level=warning msg="pkg/chroot: error unmounting \"/tmp/buildah520693946/mnt/rootfs\": error checking if \"/tmp/buildah520693946/mnt/rootfs/sys/fs/cgroup/blkio\" is mounted: no such file or directory"
time="2019-09-26T01:27:02Z" level=warning msg="pkg/bind: error unmounting \"/tmp/buildah520693946/mnt/rootfs\": error checking if \"/tmp/buildah520693946/mnt/rootfs/sys/fs/cgroup/blkio\" is mounted: no such file or directory"
STEP 7: USER 185
~~~

It seems to build the image successfully.

What does the warning mean? Can I suppress the warning message?

How reproducible:

~~~
$ git clone https://github.com/jboss-openshift/openshift-quickstarts.git
$ cd openshift-quickstarts/tomcat-websocket-chat/
$ mvn clean package
$ mkdir -p ocp/deployments
$ cp target/websocket-chat.war ocp/deployments/

$ oc new-build --name=chatapp --binary openshift/jboss-webserver50-tomcat9-openshift:latest
$ oc start-build chatapp --from-dir=./ocp --follow

...
STEP 6: RUN chown -R 185:0 /tmp/src
time="2019-09-26T01:27:02Z" level=warning msg="pkg/chroot: error unmounting \"/tmp/buildah520693946/mnt/rootfs\": error checking if \"/tmp/buildah520693946/mnt/rootfs/sys/fs/cgroup/blkio\" is mounted: no such file or directory"
~~~

Actual results:

It builds an image successfully but generates warning messages.

Expected results:

It should build an image successfully without warning messages.

Additional info:

Only `RUN` instruction generates the warnings. `COPY` or `ENV` instructions do not generate the warnings.

Comment 1 Masatoshi Hayashi 2019-09-26 02:16:02 UTC
Another example on a docker strategy build:

~~~
$ oc new-build --name=sample-docker --strategy=docker --binary openshift/jboss-webserver50-tomcat9-openshift:latest
$ oc start-build sample-docker  --from-dir=. --follow
STEP 1: FROM image-registry.openshift-image-registry.svc:5000/openshift/jboss-webserver50-tomcat9-openshift:1.2
STEP 2: USER 0
STEP 3: RUN localedef -i ja_JP -c -f UTF-8 -A /usr/share/locale/locale.alias ja_JP.UTF-8
time="2019-09-25T07:49:21Z" level=warning msg="pkg/chroot: error unmounting \"/tmp/buildah410640479/mnt/rootfs\": error checking if \"/tmp/buildah410640479/mnt/rootfs/sys/fs/cgroup/rdma\" is mounted: no such file or directory"
time="2019-09-25T07:49:21Z" level=warning msg="pkg/bind: error unmounting \"/tmp/buildah410640479/mnt/rootfs\": error checking if \"/tmp/buildah410640479/mnt/rootfs/sys/fs/cgroup/rdma\" is mounted: no such file or directory"
~~~

Comment 2 Adam Kaplan 2019-09-26 14:00:46 UTC
I'm fairly certain these are coming from buildah. @Nalin if these messages are not meaningful (or even expected?), can they be suppressed?

Comment 4 Adam Kaplan 2020-01-22 15:42:39 UTC
Duplicates #1772179

*** This bug has been marked as a duplicate of bug 1772179 ***


Note You need to log in before you can comment on or make changes to this bug.