Failed to unmount on clean up when building Centos8 IPA image on Docker
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
diskimage-builder |
New
|
Undecided
|
Unassigned |
Bug Description
At CERN, we use privileged docker containers to setup and isolate diskimage-builder environments. Lately, we noticed that when building Centos8 based IPA image, the build process fails to clean up with the following error:
```
2020-07-10 10:16:30.967 | umount: /tmp/dib_
2020-07-10 10:16:30.967 | (In some cases useful info about processes that use
2020-07-10 10:16:30.967 | the device is found by lsof(8) or fuser(1))
```
While the image is built successfully, this is still inconvenient.
I tried various different environments, but I still get this error:
- docker image based on any OS centos7 and centos8
- using docker host based on centos7 and centos8 or ubuntu
- used both diskimage-
This issues does not happen when building Centos7 image.
I am only able to build an Centos8 image without getting an error if I do not use docker and execute diskimage-builder on the server directly, but this does not give us the isolation we want.
This is how we run docker:
```
docker run -v /dev:/dev --privileged --mount source=
```
This is the script how we execute the command:
```
mkdir -p /ironic-
export ELEMENTS_
# Setup enviroment
pip install -U pip || true
pip install virtualenv || true
virtualenv $SCRIPT_
source $SCRIPT_
pip install git+https:/
# Debug
export DIB_DEV_
export DIB_DEV_
export DIB_DEV_
export DIB_DEBUG_TRACE=1
export BUILD_LOG=
# Configuration of DIB elements
export DIB_REPOREF_
export DIB_REPOREF_
# To be able to build latest release, use python 3
export DIB_PYTHON_
export DIB_RELEASE=8
export DIB_DISTRIBUTIO
disk-image-create -o /ironic-
devuser \
disable-selinux \
centos \
ironic-
ironic-
local-config \
cleanup-
ironic-rsyslog \
mellanox \
development
docker-ce | tee $BUILD_LOG
```
Let us know if there is solution to this problem or another way to isolate and sandbox the build process.
Did you have a chance to check what is keeping tmp busy?