feat: add exposed_ports to oci_image

[gzm0]

Fixes #220.

[gzm0]

Seems this fails with bazelmod. I'm investigating.

[gzm0]

Seems like under bzlmod, we're not using LATEST_CRANE_VERSION:

rules_oci/MODULE.bazel

Line 14 in 1fce184

oci.toolchains(crane_version = "v0.14.0")

Is this deliberate?

[gzm0]

I have bumped the crane version in the MODULE.bazel of the e2e test. The test passes locally. Let's see what CI says.

If you are concerned with the test not testing with the lowest supported crane version anymore, I'm happy to split it out.

This is a separate discussion, but I find the choice of toolchain version management under bzlmod odd: I'd expect that by default, I'd get the latest known versions (but the ability to downgrade the versions if necessary).

[trym-b]

Thank you for adding this feature.

Is there anything blocking this PR?
I would like to get my hands on this feature as I have some container images that I need to convert to bazel that require exposing some ports (more specifically this).

[thesayyn]

We'll unblock this shortly this week. We need to upgrade the crane version which is an undocumented public API contract we never intended to expose. We'll have to document it and tell users to register their own toolchains if they rely on a specific version of crane.

[salrashid123]

I don't think this in included in the latest 1.4.3 release but its cited in the docs as supported already.

When is the next release going out?