-
Notifications
You must be signed in to change notification settings - Fork 489
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Volume path parsing seems broken #222
Comments
what happens when you add a
? |
@elmariachi111 I don't see any change. This still does the same thing when parsing the volume path unfortunately. |
replacing the I also added a bind-propagation parameter |
Please don't close the issue because a workaround has been found, when the issue is still valid. I've encountered the same now, and the fix was indeed replacing |
The issue on the code seems to get fixed when using |
would you please confirm that this bug is still there in latest code? |
yeap. The bug still persists. tried it with the latest master branch. |
the following are equivalent and ./ or multiple /// are valid
despite that I'll fix it |
In the docker-compose.yml, under the volumes I have the following
When running
podman-compose up
I see that the path of the volume gets tangled up and instead of getting$(pwd)/environment/configuration/app.json
, I see$(pwd)/./environment/configuration/app.json
and this way the container cannot cannot start.Environment
OS/Distro: Fedora 32
Podman version:
podman-compose version:
Maybe it's something worth taking a look into.
When running
docker-compose up
it seems to start the container just fine.The text was updated successfully, but these errors were encountered: