Update the pypi version to 1.1.0 because the 1.0.6 version does not support the Compose specification for env_file

[andrew-ma]

Update the pypi version to 1.1.0 because the 1.0.6 version does not support the Compose specification for env_file

[manics]

There's no automated GitHub workflow to publish the PyPI package, is it handled manually?

[luckylinux]

I also have this Issue (related to podman + network_mode: "pasta:[options]" Networking not working correctly prior to 1.1.0).

Workaround 😃:

# (Optional) Create a Dedicated Python venv
(podman-compose) podman@HOST:~$ python -m venv ~/podman-compose
(podman-compose) podman@HOST:~$ source ~/podman-compose/bin/activate

# Install Podman Compose
(podman-compose) podman@HOST:~$ pip install git+https://github.com/containers/[email protected]

# Print Version
(podman-compose) podman@HOST:~$ podman-compose --version
podman-compose version 1.1.0
podman version 4.9.4

On a Separate Note, this does NOT work 😞:

# Create User ~/.local/bin Folder if not existing yet
podman@HOST:~$ mkdir -p ~/.local/bin

# Follow Manual Setup Instructions
podman@HOST:~$ curl -o ~/.local/bin/podman-compose https://raw.githubusercontent.com/containers/podman-compose/main/podman_compose.py
podman@HOST:~$ chmod +x ~/.local/bin/podman-compose

# Test
/usr/local/bin/podman-compose --version
Traceback (most recent call last):
  File "/usr/local/bin/podman-compose", line 5, in <module>
    from podman_compose import main
ModuleNotFoundError: No module named 'podman_compose'

Not sure if it's a podman-compose vs podman_compose (dash vs underscore) issue that is NOT correctly handled by Python and/or podman-compose.

[luckylinux]

@andrew-ma: are you sure you need podman-compose Version 1.1.0 to get the env_file Directive working ? I used env_file several Times with podman-compose Version 1.0.6 without Issues ...

EDIT: this is what I usually use

version: '3'

services:
  <myservice>:
    ...
    env_file:
      - .env
    ...

It also works with podman-compose Version 1.0.6 (NOT sure about 1.0.3).

On the other Hand your version of podman is quite old (for a very brief Period I ran podman Version 4.3.1 on Debian Bookworm 12, then I "upgraded" using APT Pinning to Debian Testing currently feaeturing podman 4.9.4).

Fedora just got podman Version 5.1.0 😃.

[andrew-ma]

Ok yeah didn’t know it was working with 1.0.6. If so that would be great then. Thanks for your response!

…

On Tue, Jun 11, 2024 at 2:43 AM luckylinux ***@***.***> wrote: @andrew-ma <https://github.com/andrew-ma>: are you sure you need podman-compose Version 1.1.0 to get the env_file Directive working ? I used env_file several Times with podman-compose Version 1.0.6 without Issues ... — Reply to this email directly, view it on GitHub <#948 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AEUJT4RB2JENLOTIGE5COI3ZG2MARAVCNFSM6AAAAABIJM4FAWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNJZHEYTONRYGA> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[luckylinux]

@andrew-ma: well I thought it was ... and it is ... but only if the file is named .env:

env_file:
  - .env

I was trying to get Nautobot Example running with Podman (long story ... not working yet) and there they used 2 .env files (local.env and creds.env and those were NOT recognized).

Similarly when I was trying to feed Caddy some Environment Variables: caddy.env was getting ignored, .env worked correctly).

So I think you are right, if the file is NOT .env (or maybe also other files are supported ? .env.xxx or .xxx.env ???).