-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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 mount of '.' uses internal directory #3504
Labels
kind/bug
Categorizes issue or PR as related to a bug.
locked - please file new issue/PR
Assist humans wanting to comment on an old issue or PR with locked comments.
Comments
openshift-ci-robot
added
the
kind/bug
Categorizes issue or PR as related to a bug.
label
Jul 6, 2019
Hmm. Probably due to it being runc that uses the paths - I'm pretty sure it
runs in that directory so it can easily find the OCI spec.
Easy solution is to convert relative paths to absolute as early as we can,
so we get Podman's current directory.
…On Sat, Jul 6, 2019, 06:30 Reuben Lifshay ***@***.***> wrote:
/kind bug
When using . as the source of a volume mount podman seems to use a podman
related directory for the mount instead of either using the current
directory or throwing an error.
*Steps to reproduce the issue:*
$ podman run --rm -v .:/test -it alpine
/ # ls -la /test/
total 36
drwx------ 4 root root 4096 Jul 6 10:18 .
drwxr-xr-x 1 root root 4096 Jul 6 10:18 ..
drwxr-xr-x 2 root root 4096 Jul 6 10:18 artifacts
srwx------ 1 root root 0 Jul 6 10:18 attach
-rw-r--r-- 1 root root 20428 Jul 6 10:18 config.json
prw-r--r-- 1 root root 0 Jul 6 10:18 ctl
-rw------- 1 root root 735 Jul 6 10:18 ctr.log
drwxrwxrwt 2 root root 40 Jul 6 10:18 shm
/ #
*Output of podman version:*
Version: 1.4.3
RemoteAPI Version: 1
Go Version: go1.10.4
OS/Arch: linux/amd64
*Output of podman info --debug:*
debug:
compiler: gc
git commit: ""
go version: go1.10.4
podman version: 1.4.3
host:
BuildahVersion: 1.9.0
Conmon:
package: 'conmon: /usr/bin/conmon'
path: /usr/bin/conmon
version: 'conmon version 0.3.0, commit: unknown'
Distribution:
distribution: ubuntu
version: "18.04"
MemFree: 3911909376
MemTotal: 16775352320
OCIRuntime:
package: 'cri-o-runc: /usr/bin/runc'
path: /usr/bin/runc
version: 'runc version spec: 1.0.1-dev'
SwapFree: 2147479552
SwapTotal: 2147479552
arch: amd64
cpus: 8
hostname: computator
kernel: 4.15.0-54-generic
os: linux
rootless: true
uptime: 5h 46m 46.17s (Approximately 0.21 days)
registries:
blocked: null
insecure: null
search:
- docker.io
store:
ConfigFile: /home/user/.config/containers/storage.conf
ContainerStore:
number: 0
GraphDriverName: overlay
GraphOptions: null
GraphRoot: /home/user/.local/share/containers/storage
GraphStatus:
Backing Filesystem: extfs
Native Overlay Diff: "false"
Supports d_type: "true"
Using metacopy: "false"
ImageStore:
number: 2
RunRoot: /run/user/1000
VolumePath: /home/user/.local/share/containers/storage/volumes
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#3504>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AB3AOCBCKL5ERPWERPSFD6DP6BX2RANCNFSM4H6TEAAA>
.
|
@QiWang19 Can you fix this? |
QiWang19
added a commit
to QiWang19/podman
that referenced
this issue
Jul 10, 2019
fix containers#3504 If --volume host:dest host is not a named volume, convert the host to a absolute directory path. Signed-off-by: Qi Wang <[email protected]>
github-actions
bot
added
the
locked - please file new issue/PR
Assist humans wanting to comment on an old issue or PR with locked comments.
label
Sep 24, 2023
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
kind/bug
Categorizes issue or PR as related to a bug.
locked - please file new issue/PR
Assist humans wanting to comment on an old issue or PR with locked comments.
/kind bug
When using
.
as the source of a volume mount podman seems to use a podman related directory for the mount instead of either using the current directory or throwing an error.Steps to reproduce the issue:
Output of
podman version
:Output of
podman info --debug
:The text was updated successfully, but these errors were encountered: