Re: [atomic-devel] atomic scan unable to unmount image under /run/atomic/

[Brent Baude <bbaude redhat com>]

On Wed, 2017-07-12 at 15:14 +0530, Dharmit Shah wrote:
> Hi,
> 
> We've been using this [1] scanner for some time now. So far, we've
> never
> faced any issue with it.
> 
> Recently we started seeing an issue wherin once atomic scan mounts
> the
> container image under `/run/atomic`, the unmount doesn't happen
> successfully. It errors out with read-only file system message [2].
> The
> entry is visible in `df -h` output in the same pastebin.
> 
> Other scanners we're using [3] don't seem to be facing this issue and
> I
> can see mount point at `/run/atomic` getting free. This particular
> scanner is different from others in that it first uses atomic mount
> to
> mount the container image in read-write mode at certain location. No
> other scanner has this read-write requirement. However, this was
> never
> an issue so far.
> 
> I'm not certain if this is an issue with atomic or device-mapper or
> my
> code. I'm using CentOS 7.3 and atomic-1.17.2-9.git2760e30.el7.x86_64.
> Let me know if I need to provide additional info.
> 
> Regards,
> Dharmit
> 
> [1]
> https://github.com/CentOS/container-pipeline-service/tree/master/atom
> ic_scanners/pipeline-scanner
> [2] http://pastebin.centos.org/123896/
> [3]
> https://github.com/CentOS/container-pipeline-service/tree/master/atom
> ic_scanners/
> 


Dharmit,

I'd like to see a log of the entire op, including running atomic --
debug when you perform the scan.  For certain, atomic-1.17 is getting
fairly old.  Do you get the same result on say Fedora?

anyways, I can help you ... we can take this off list if you like ...
hit me up on irc