Muayyad Alsadi

as you can see around line 301, labels are added unconditionally when creating the volumes (there is no other place that creates them) https://github.com/containers/podman-compose/blob/v1.0.3/podman_compose.py#L301 would you please share results of...

you can remove those by filtering `dangling` volumes ``` podman volume ls --noheading --format '{{.Name}}' --filter dangling=true | xargs podman volume rm ``` are you sure docker-compose track those volumes?

@disaster123 Please send me pull request

Please consider upgrading to 1.x using pip, you can do that rootless. ``` pip3 install --upgrade --user podman-compose ``` So basically you want a good way to pass keep-id. You...

@dngray please test latest devel branch It now passes `PODMAN_*` from `.env` to podman Most likely you don't need to set `USER: ${USER:-0}`

> Permissions look okay: Consider 711 ``` chmod 711 /home/daniel ```

@dngray I've tested 700 and it worked too my .env ``` PODMAN_USERNS=keep-id ``` my compose ```yaml version: '3' services: web: image: busybox command: httpd -f -p 8123 -h /etc/ network_mode:...

> Installed via? Yes correct. This is the way. Try ``` podman-compose exec web whoami podman-compose exec web id ``` Could this be selinux issue? Or silverblue / ostree related?

what can we do form our side (as far as compose is concerned)? could it be SELinux?

any update?