Podman: Conflict at mount destination with podman 1.3.1

[vsim3]

Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)

/kind bug

Description

Podman 1.3 error with docker postgres:10-alpine image
Upgrade to f30 lead to postgresql container error
_ Work fine on v1.2

Steps to reproduce the issue:

1. sudo podman run -d --name rss-postgresdb --cap-drop=CAP_NET_BIND_SERVICE --cap-drop=CAP_NET_RAW --conmon-pidfile=${DB_PID} -v ${PGDATA}:/var/lib/postgresql/data:Z -e POSTGRES_USER=postgres -e POSTGRES_PASSWORD=${PW} -e POSTGRES_DB=db --uidmap=0:100000:65536 --gidmap=0:100000:65536--oom-score-adj="-1000" -p 127.0.0.1:5432:5432 docker.io/library/postgres:10-alpine

Describe the results you received:
Error: conflict at mount destination /var/lib/postgresql/data: duplicate mount destination

podman version:
podman-1.3.1-1.git7210727.fc30
```

[cwawak]

Also seeing the same behavior on the same version - this was a clean Fedora 30 server minimal install. Also on 1.3.1-1-git7210727.fc30.x86_64. Specifying a volume using -v always results in this error.

[mheon]

This was my code, I'll take a look.

[mheon]

Image volumes - has to be image volumes.

We have a named volume from an image volume at /var/lib/postgresql/data and an explicit user-specified mount at /var/lib/postgresql/data and we're not properly handling the conflict.

Working up a patch.

[cwawak]

@mheon this is exactly what's going on - thank you so much for taking a look, and allowing me to have choice in my container life. 👍

[mheon]

3177 should fix

[langdon]

Is there a work around for this while we wait for the patch to land?

[mheon]

Try --image-volume=tmpfs - it should make the conflict one that Podman is able to automatically resolve.

[langdon]

that worked! thanks!

[vsim3]

Thanks for that quick fix.

[rhatdan]

@mheon Do we need a new release for this? Is this worth blocking podman 1.3.1?

[TomSweeneyRedHat]

+1 on the new release from me, blocking I'm on the fence for.

[mheon]

We just merged a few big PRs from Giuseppe on user namespace, so I think
our best bet is to try and cut a 1.4 next week with whatever is ready and
get that it quickly.

On Wed, May 22, 2019, 08:50 Tom Sweeney [e-mail] wrote:

+1 on the new release from me, blocking I'm on the fence for.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/containers/libpod/issues/3174?email_source=notifications&email_token=AB3AOCCPM4QNRYSMZUXYUM3PWU6PVA5CNFSM4HOKQLN2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODV654LI#issuecomment-494788141,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AB3AOCGPTT3YF5DSPMZPEALPWU6PVANCNFSM4HOKQLNQ
.