You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a compose file like this (trimmed down for only relevant parts):
# based ob https://github.com/orangecoding/fredy/blob/7ebd73c9cf209b57f667cd168f8d18c3e2e1001c/docker-compose.ymlservices:
fredy:
image: ghcr.io/orangecoding/fredy # map existing config and databasevolumes:
- db:/dbvolumes:
db:
Save this in a directory named fredy.(IIRC this is relevant for the default project name of docker compose files/projects.)
Now running this with podman-compose up vs podlet shows some differences:
podman-compose creates a container named fredy_fredy_1 and creates fredy_db as a volume
podlet (and podman/systemd/podman-systemd-generator etc. aka the whole pipeline) on the other hand creates a container named systemd-fredy and creates db as a volume name
Issues
I don't really care about the container name, but the volume name being different means both access different data. This is unfortunate, as it means it makes switching from one to another harder. Also, I have not tested Docker to see what name it uses but I guess docker-compose is more correct here, if I read the Docker doc correctly.
Also, as you can see below podlet also does not make it set some default labels (which may be fine for me, just saw that differs too).
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I have a compose file like this (trimmed down for only relevant parts):
Save this in a directory named
fredy
.(IIRC this is relevant for the default project name of docker compose files/projects.)Now running this with
podman-compose up
vspodlet
shows some differences:fredy_fredy_1
and createsfredy_db
as a volumesystemd-fredy
and createsdb
as a volume nameIssues
I don't really care about the container name, but the volume name being different means both access different data. This is unfortunate, as it means it makes switching from one to another harder. Also, I have not tested Docker to see what name it uses but I guess
docker-compose
is more correct here, if I read the Docker doc correctly.Also, as you can see below podlet also does not make it set some default labels (which may be fine for me, just saw that differs too).
Details
Additional ideas
A workaround by using some more keys to override the name unfortunately also is not supported, see #158
System
Beta Was this translation helpful? Give feedback.
All reactions