network_mode: host have no effect and ports does not opened (podman-compose 1.0.3) #397

Hubbitus · 2022-01-02T15:06:47Z

Describe the bug

Despite to the container used network_mode: host default network is also applied in the command line later and has precedence!

To Reproduce

Minimal docker-compose.yml file to reproduce problem:

version: '2.4'
services:
    apache:
        container_name: podman-compose-bug-reproduce
        image: docker.io/httpd:2.4.52
#        ports:
#            - 80:80
        # To use ports less than 1024 in rootless mode that require allow priveledged ports use. E.g. (or similar in sysctl.conf):
        # sudo sysctl net.ipv4.ip_unprivileged_port_start=70
        network_mode: host
        hostname: 127.0.0.1

Run it:

$ podman-compose up -d
['podman', '--version', '']
using podman version: 3.4.4
** excluding:  set()
['podman', 'network', 'exists', 'podman-compose-bug_default']
podman run --name=podman-compose-bug-reproduce -d --label io.podman.compose.config-hash=123 --label io.podman.compose.project=podman-compose-bug --label io.podman.compose.version=0.0.1 --label com.docker.compose.project=podman-compose-bug --label com.docker.compose.project.working_dir=/home/pasha/temp/podman-compose-bug --label com.docker.compose.project.config_files=docker-compose.yml --label com.docker.compose.container-number=1 --label com.docker.compose.service=apache --network host --net podman-compose-bug_default --network-alias apache --hostname 127.0.0.1 docker.io/httpd:2.4.52
72d9447da5d9680142c1ad64388d9bcff1791e0d6a2d4ba44d7094b813164667
exit code: 0

Test:

$ http http://localhost

http: error: ConnectionError: HTTPConnectionPool(host='localhost', port=80): Max retries exceeded with url: / (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7fe68286f070>: Failed to establish a new connection: [Errno 111] Connection refused')) while doing a GET request to URL: http://localhost/

Expected behavior

Get working Apache httpd welcome page.

Actual behavior

Got an error what the port is not open.

Please note, in the actual command line for the podman present sequentially: --network host --net podman-compose-bug_default, so if I manually re-run such container without --net podman-compose-bug_default that will work:

$ podman rm -vf podman-compose-bug-reproduce
72d9447da5d9680142c1ad64388d9bcff1791e0d6a2d4ba44d7094b813164667
$ podman run --name=podman-compose-bug-reproduce -d \
  --label io.podman.compose.config-hash=123 --label io.podman.compose.project=podman-compose-bug --label io.podman.compose.version=0.0.1 --label com.docker.compose.project=podman-compose-bug --label com.docker.compose.project.working_dir=/home/pasha/temp/podman-compose-bug --label com.docker.compose.project.config_files=docker-compose.yml --label com.docker.compose.container-number=1 --label com.docker.compose.service=apache \
  --network host --network-alias apache \
  --hostname 127.0.0.1 docker.io/httpd:2.4.52
855ef370efc9101aa69768b06f1300cf1ea5730c8e26f4e358269e23d31bc4f6
[pasha@hubbitus podman-compose-bug]$ http http://localhost
HTTP/1.1 200 OK
Accept-Ranges: bytes
Connection: Keep-Alive
Content-Length: 45
Content-Type: text/html
Date: Sun, 02 Jan 2022 15:01:26 GMT
ETag: "2d-432a5e4a73a80"
Keep-Alive: timeout=5, max=100
Last-Modified: Mon, 11 Jun 2007 18:53:14 GMT
Server: Apache/2.4.52 (Unix)

<html><body><h1>It works!</h1></body></html>

I also tested that behaviour with previous version of podman-compose (in Fedora 35 that is 0.1.8), and it generate expected (working) run command, please look:

$ sudo dnf downgrade podman-compose -y
...
Downgraded:
  podman-compose-0.1.8-1.fc35.noarch                                                                                                                                                                                                                                          
Complete!
$ podman-compose down
...
$ podman-compose up -d
['podman', '--version', '']
using podman version: 3.4.4
** excluding:  set()
podman pod create --name=podman-compose-bug --share net --infra-name=podman-compose-bug_infra
6aaa607fc4e2f6281d8a8b49f6005f65eb80c78fe575f17c1a8e68cd36c13d4e
exit code: 0
podman run --name=podman-compose-bug-reproduce -d --pod=podman-compose-bug --label io.podman.compose.config-hash=123 --label io.podman.compose.project=podman-compose-bug --label io.podman.compose.version=0.0.1 --label com.docker.compose.project=podman-compose-bug --label com.docker.compose.project.working_dir=/home/pasha/temp/podman-compose-bug --label com.docker.compose.project.config_files=docker-compose.yml --label com.docker.compose.container-number=1 --label com.docker.compose.service=apache --network host --add-host apache:127.0.0.1 --add-host podman-compose-bug-reproduce:127.0.0.1 --hostname 127.0.0.1 docker.io/httpd:2.4.52
4ea496ef388f8c20793f8a6027d3308f8a5e3f0af2ef4c25008819930442a6a9
exit code: 0

[pasha@hubbitus podman-compose-bug]$ http http://localhost
HTTP/1.1 200 OK
...

<html><body><h1>It works!</h1></body></html>

Versions and environment

$ podman-compose version
using podman version: 3.4.4
podman-composer version  1.0.3
podman --version 
podman version 3.4.4
exit code: 0...

Environment:

OS: Fedora Linux 35
podman version: 3.4.4
podman compose version: 1.0.3

The text was updated successfully, but these errors were encountered:

Hubbitus · 2022-01-02T15:07:46Z

Possibly (unsure) related to #316

muayyad-alsadi · 2022-01-02T16:18:59Z

it seems that --network host and --net podman-compose-bug_default canceled each other
I'll see what I can do.

NoTuxNoBux · 2022-01-04T11:44:11Z

I'm also encountering a similar (related?) issue without --network host in compose.yaml from versions 1.0.2 and upward; most of my applications start properly, but the PostgreSQL service from my compose.yaml doesn't have its port properly reachable - not by the other applications in the compose.yaml, nor from my host on the port mapped there (5432).

I see the following line is no longer printed on up:

podman pod create --name=myproject --share net -p 3000:3000 -p 3001:3001 -p 5432:5432 -p 3002:3002 -p 8080:8080 -p 3003:3003

Instead, all the separate containers get something like the following, which wasn't the case before:

--net myproject_default --network-alias postgresql -p 5432:5432

The applications are all reachable on their respective ports (3000, 3001, 3002, and 8080), but they don't seem to share the same network any more somehow.

muayyad-alsadi · 2022-01-04T12:51:18Z

@NoTuxNoBux please check this

#379

NoTuxNoBux · 2022-01-04T13:34:17Z

@muayyad-alsadi That was it, thanks, and sorry for the noise.

In case anyone else experiences my problem, on Arch:

Install podman-dnsname from the official repositories (podman-compose doesn't depend on it so it doesn't install automatically).
Stop all your containers.
Existing networks still won't use the newly installed dnsname plugin and they aren't removed automatically on podman-compose down, so explicitly remove all your networks using podman network rm (use podman network ls to see them) to force them to be recreated and upgrade.
Run podman-compose up, which should automatically recreate the network, and it should now properly resolve hostnames.

muayyad-alsadi · 2022-01-12T13:45:33Z

@Hubbitus please test the above commit

quexten · 2022-01-29T22:10:13Z

@muayyad-alsadi I was experiencing the same issue. With the latest development version, this works, however another related issue seems to be with network_mode: container:test. On the latest stable version, this results in two net flags, the correct one and the --net test-test_default one. On the development version, only the second flag is present. The expected outcome would be only the "--net container:test" flag being present.

Edit: Actually, since this seems to be an entirely new feature, I opened a separate issue for this: #413

muayyad-alsadi · 2022-01-30T12:54:00Z

@quexten you can use "network_mode: service:test" in latest devel

transtone · 2022-11-14T06:52:13Z

@quexten you can use "network_mode: service:test" in latest devel

Is there a plan to release 1.0.4?

julyclyde · 2023-03-03T07:26:02Z

I'm using 1.0.3 RPM from Almalinux and meet the bug either. I want to keep my system clean, and don't want to PIP install podman-compose. Could you release next version ASAP?

nerijus · 2023-05-16T10:59:15Z

1.0.6 is released and it works ok.

Hubbitus added the bug Something isn't working label Jan 2, 2022

muayyad-alsadi closed this as completed in 15e0ab9 Jan 12, 2022

muayyad-alsadi mentioned this issue Jan 18, 2022

network_mode=host is not working as expected #406

Closed

whitingjr mentioned this issue Feb 14, 2022

podman-compose upgrade breaks Prerequisites instructions. Hyperfoil/Horreum#117

Closed

gdlol mentioned this issue Jun 25, 2022

Podman/Podman-compose support? gdlol/MessageHub#11

Open

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

network_mode: host have no effect and ports does not opened (podman-compose 1.0.3) #397

network_mode: host have no effect and ports does not opened (podman-compose 1.0.3) #397

Hubbitus commented Jan 2, 2022 •

edited

Loading

Hubbitus commented Jan 2, 2022

muayyad-alsadi commented Jan 2, 2022

NoTuxNoBux commented Jan 4, 2022 •

edited

Loading

muayyad-alsadi commented Jan 4, 2022

NoTuxNoBux commented Jan 4, 2022

muayyad-alsadi commented Jan 12, 2022

quexten commented Jan 29, 2022 •

edited

Loading

muayyad-alsadi commented Jan 30, 2022

transtone commented Nov 14, 2022

julyclyde commented Mar 3, 2023

nerijus commented May 16, 2023

network_mode: host have no effect and ports does not opened (podman-compose 1.0.3) #397

network_mode: host have no effect and ports does not opened (podman-compose 1.0.3) #397

Comments

Hubbitus commented Jan 2, 2022 • edited Loading

Describe the bug

To Reproduce

Expected behavior

Actual behavior

Versions and environment

Environment:

Hubbitus commented Jan 2, 2022

muayyad-alsadi commented Jan 2, 2022

NoTuxNoBux commented Jan 4, 2022 • edited Loading

muayyad-alsadi commented Jan 4, 2022

NoTuxNoBux commented Jan 4, 2022

muayyad-alsadi commented Jan 12, 2022

quexten commented Jan 29, 2022 • edited Loading

muayyad-alsadi commented Jan 30, 2022

transtone commented Nov 14, 2022

julyclyde commented Mar 3, 2023

nerijus commented May 16, 2023

Hubbitus commented Jan 2, 2022 •

edited

Loading

NoTuxNoBux commented Jan 4, 2022 •

edited

Loading

quexten commented Jan 29, 2022 •

edited

Loading