How to create a VLAN tagged network device for a container?

[mpeter50]

When I wanted to create a network device through which the container only has access to a specific VLAN, I could use this with Docker:

# docker network create --driver macvlan --opt parent=eth0.5 --subnet=172.16.0.0/24 --gateway=172.16.0.1 macvlan_vlan5_test

But if similarly I do this with rootful Podman, I get an error that the subinterface does not exist:

# podman network create --driver macvlan --ipam-driver dhcp --opt parent=eth0.5 macvlan_vlan5_test
Error: parent interface eth0.5 does not exist

The difference is that Docker creates the subinterface, and Podman does not.

What is the recommended way to create a VLAN tagged interface for a Podman container?

I use Podman 4.9.5, but had the same expereince with 5.6.2 on a test system.

[mpeter50]

Looking at the documentation what I have found so far is that the bridge network driver accepts a vlan option that may be what I am looking for: https://docs.podman.io/en/v4.4/markdown/podman-network-create.1.html#opt-o-option
Is this the correct way?

What I found strange is that here its handled by not the macvlan driver, but by the bridge driver. What is the difference between Docker's and Podman's way of handling this?
I have a hunch that Docker's way is what man ip link describes in the "MACVLAN and MACVTAP Type Support" section, and Podman's way is whats described at "BRIDGE Type Support" and its vlan_filtering option on the same man page. Is that right?