Handle string ports in docker compose v2 config yaml

[jsoriano]

Using docker-compose v2.3.x (go implementation), elastic-package shellinit fails with:

Error: shellinit failed: could not get Docker Compose configuration for service: could not unmarshal YAML map node: yaml: unmarshal errors:
  line 4: cannot unmarshal !!str `9200` into int

This seems to happen because some ports are represented as strings in the docker-compose config output.

Support both versions by allowing ports to be integers or numbers.

[elasticmachine]

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2022-03-23T08:56:52.573+0000

• Duration: 23 min 39 sec

Test stats 🧪

Test	Results
Failed	0
Passed	618
Skipped	1
Total	619

🤖 GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.

[mtojek]

Is this the moment, when we should use Compose V2 in general for CI testing?

[jsoriano]

Is this the moment, when we should use Compose V2 in general for CI testing?

I think we are close, the main blocker I have found so far with v2 has been not being able to use elastic-package shellinit, what would be solved by this PR.
Apart of that, installation of packages during tests fail on my laptop, as if docker compose is not correctly recreating the package registry after packages are built. I would have to investigate this a bit more.

Something we might also investigate is to use the Go API 🙂, so we don't depend on the installed binary.

[jsoriano]

/test

[jsoriano]

Actually this may be a bug in docker compose. This is the documented format:

    - mode: ingress
      target: 80
      published: 80
      protocol: tcp

This is what I am finding:

    - mode: ingress
      host_ip: 127.0.0.1
      target: 9200
      published: "9200"
      protocol: tcp

[jsoriano]

Open issue in docker compose project: docker/compose#9306