podman libpod REST API - passing folders as volumes results in error

[PedroM25]

Hello everyone,
Using the Libpod API of the Podman RESTful API, I am trying to create a container.

On the command line, when I run the following commands:

sudo mkdir -p /opt/podman && sudo chown $USER:$USER /opt/podman && sudo mkdir -p /opt/podman/test1

podman create -t --net host --name test1 -v /var/run/dbus:/var/run/dbus -v /opt/podman/test1:/var/persistent/my-company docker.io/library/busybox:latest; podman start test1

Everything works fine.

However, when using the REST API and doing:

podman system service --time=0 unix:/run/user/$UID/podman/podman.sock

curl --unix-socket /run/user/1000/podman/podman.sock -X POST http://d/v4.9.3/libpod/containers/create -H "Content-Type: application/json" -d '{ "terminal": true, "network_options": { "host": [] }, "name": "test1", "volumes": [ { "Dest": "/var/run/dbus", "Name": "/var/run/dbus" }, { "Dest": "/var/persistent/my-company", "Name": "/opt/podman/test1" } ], "image": "docker.io/library/busybox:latest" }'

I get the error:

{"cause":"invalid argument","message":"creating named volume \"/var/run/dbus\": running volume create option: names must match [a-zA-Z0-9][a-zA-Z0-9_.-]*: invalid argument","response":500}

Looking at the --volume parameter documentation, you can see that:

"If a volume source is specified, it must be a path on the host or the name of a named volume. [...] Any source that does not begin with a . or / is treated as the name of a named volume."

So, my question is, does the Libpod API support folders on host as volumes?
Or only compat API allows for this?

[Luap99]

you need to use mounts, volume is onlt for actual real named volumes in the API.

For example

 "mounts": [
  {
   "destination": "/test",
   "type": "bind",
   "source": "/home/pholzing",
   "options": [
    "rw"
   ]
  }

The cli and API do not match one to one especially not around mounting.

[PedroM25]

yup that's it! thank you!