OPM fails to create a pruned index image

[jforce]

Bug Report

What did you do?
Following the below linked documentation I'm attempting to create a custom pruned index image of 3 operators, but unfortunately not having much luck as it errors out mid process.

https://docs.openshift.com/container-platform/4.6/operators/admin/olm-restricted-networks.html

opm index prune \
    -f registry.redhat.io/redhat/redhat-operator-index:v4.6 \
    -p cluster-logging,elasticsearch-operator,metering-ocp \
    -t localhost:5000/olm/redhat-operator-index:v4.6 
INFO[0000] pruning the index                             packages="[cluster-logging elasticsearch-operator metering-ocp]"
INFO[0000] Pulling previous image registry.redhat.io/redhat/redhat-operator-index:v4.6 to get metadata  packages="[cluster-logging elasticsearch-operator metering-ocp]"
INFO[0000] running /usr/bin/podman pull registry.redhat.io/redhat/redhat-operator-index:v4.6  packages="[cluster-logging elasticsearch-operator metering-ocp]"
INFO[0003] running /usr/bin/podman pull registry.redhat.io/redhat/redhat-operator-index:v4.6  packages="[cluster-logging elasticsearch-operator metering-ocp]"
INFO[0006] Getting label data from previous image        packages="[cluster-logging elasticsearch-operator metering-ocp]"
INFO[0006] running podman inspect                        packages="[cluster-logging elasticsearch-operator metering-ocp]"
INFO[0006] running podman create                         packages="[cluster-logging elasticsearch-operator metering-ocp]"
INFO[0006] running podman cp                             packages="[cluster-logging elasticsearch-operator metering-ocp]"
INFO[0017] running podman rm                             packages="[cluster-logging elasticsearch-operator metering-ocp]"
Error: open index_tmp_500513138/database/index.db: no such file or directory
Usage:
  opm index prune [flags]

Flags:
  -i, --binary-image opm        container image for on-image opm command
  -c, --container-tool string   tool to interact with container images (save, build, etc.). One of: [docker, podman] (default "podman")
  -f, --from-index string       index to prune
      --generate                if enabled, just creates the dockerfile and saves it to local disk
  -h, --help                    help for prune
  -d, --out-dockerfile string   if generating the dockerfile, this flag is used to (optionally) specify a dockerfile name
  -p, --packages strings        comma separated list of packages to keep
      --permissive              allow registry load errors
  -t, --tag string              custom tag for container image being built

Global Flags:
      --skip-tls   skip TLS certificate verification for container image registries while pulling bundles or index

I do appear to have a 'index_tmp_500513138' directory created but no 'database' sub directory, only 'merged'.

What did you expect to see?
A new local pruned image

What did you see instead? Under which circumstances?
No image, and the above listed error

Environment

• opm version
  Version: version.Version{OpmVersion:"v1.14.3-5-gf6e5d92", GitCommit:"f6e5d9281f335472dda7110fca2c710794c97fb5", BuildDate:"2020-10-06T13:13:12Z", GoOs:"linux", GoArch:"amd64"}

• oc version
  Client Version: 4.6.1

• podman --version
  podman version 1.6.4

Additional context
Let me know if you require any further details and i'm happy to provide them.

[jforce]

Raised Bugzilla for tracking: https://bugzilla.redhat.com/show_bug.cgi?id=1894167
Will close this issue.