Exposing containers outside our underlying host
Container adoption in an enterprise company or a community project could be a hard thing to do that could require time. For this reason, we may not have all the required services running as containers during our adoption journey. This is why exposing containers outside our underlying host could be a nice solution for interconnecting services that live in containers to services that run in the legacy world.
As we briefly saw earlier in this chapter, Podman uses two different networking stacks, depending on the container: rootless or rootfull.
Even though the underlying mechanism is slightly different, depending on if you are using a rootless or a rootfull container, Podman's command-line options for exposing network ports are the same for both container types.
Good to Know
Note that the example we are going to see in this section will be executed as a root user. This choice was necessary because the main objective of this...
