No host port mapping after creating container #3

Activity

1. shyim commented on Dec 21, 2023

   

   shyim

   on Dec 21, 2023

   Collaborator

   More actions

   In which environment are you running PHPUnit? We use the internal IP of the container right now, so we don't have to do any port mapping :)
2. hantsy commented on Jun 7, 2024

   

   hantsy

   on Jun 7, 2024

   Last edited by hantsy

   More actions

   Testcontainer Java uses random ports if it is not set, this way can avoid port conflict. After container is started, we can get the real exposed port.
3. shyim commented on Jun 7, 2024

   

   shyim

   on Jun 7, 2024

   Collaborator

   More actions

   Do you have an link to the implementation? What do they use as "IP", that would be interesting 🤔, hard-code 127.0.0.1 🤔
4. hantsy commented on Jun 8, 2024

   

   hantsy

   on Jun 8, 2024

   More actions

   I used Testcontainers Java in projects for years, and by default when declaring a container, it will expose all ports, and map to random ports of clients(your machine), it has APIs to get the mapped ports, and first mapping port, etc.

   see: https://github.com/hantsy/spring-r2dbc-sample/blob/master/testcontainers/src/test/java/com/example/demo/PostRepositoryWithTestcontainersAnnotationsAndDynamicPropertySourceTest.java#L35
5. MaxDaten commented on Feb 13, 2025

   

   MaxDaten

   on Feb 13, 2025

   Last edited by MaxDaten

   More actions

   In which environment are you running PHPUnit? We use the internal IP of the container right now, so we don't have to do any port mapping :)

   Same problem here. I think it's macOS-specific because docker is running differently. If no exposed port maps to the host, you can't connect to the container from the host where the PHPUnit is running.

   Workaround, use withPort and localhost/127.0.0.1

   For example, should be easily adaptable to plain PDO:

   abstract class DatabaseTestCase extends TestCase
   {
   
       protected Zend_Db_Adapter_Abstract $db;
       protected MySQLContainer $container;
   
       /**
        * @throws \Zend_Db_Exception
        */
       protected function setUp(): void
       {
           $container = MySQLContainer::make('8.0');
           $container->withMySQLDatabase('foo');
           $container->withMySQLUser('bar', 'baz');
           $randomPort = rand(3300, 3400);
           $container->withPort($randomPort, 3306);
   
           $container->run();
   
           $params = [
               'host' => '127.0.0.1',
               'port' => $randomPort,
               'dbname' => 'foo',
               'username' => 'bar',
               'password' => 'baz',
               'driver_options' => [
                   PDO::ATTR_TIMEOUT => 2,
                   PDO::ATTR_ERRMODE => PDO::ERRMODE_EXCEPTION,
               ],
           ];
   
           $this->db = Zend_Db::factory(
               "pdo_mysql",
               $params
           );
           Zend_Db_Table_Abstract::setDefaultAdapter($this->db);
       }
   }
6. thoro commented on Feb 3, 2026

   

   thoro

   on Feb 3, 2026

   Last edited by thoro

   More actions

   I just ran into the same issue, I believe multiple issues come together

   1. Dockerfile does not contain EXPOSE - if the same ports are exposed as the Dockerfile exposes all, works
   2. withExposedPorts does not automatically expose ports, because it only sets the hostConfig and not the containerConfig
   3. it's not possible to expose the ports in the containerConfig, because there's a bug in the normalizer that creates an array in the json instead of an object.

   so here is a fixed containers implementation that makes it work:

   class FixedGenericContainer extends GenericContainer
   {
       protected function createContainerConfig(): ContainersCreatePostBody
       {
           $config = parent::createContainerConfig();
   
           // Set ExposedPorts on the container config
           // This is required for images that don't have EXPOSE in their Dockerfile
           if ($this->exposedPorts !== []) {
               $exposedPortsConfig = [];
               foreach ($this->exposedPorts as $port) {
                   $item = new ContainerConfigExposedPortsItem();
                   // Workaround: Add dummy key so it serializes to {"_":true} instead of []
                   // Docker accepts and ignores the extra key
                   $item['_'] = true;
                   $exposedPortsConfig[$port] = $item;
               }
               $config->setExposedPorts($exposedPortsConfig);
           }
   
           return $config;
       }
   }
   

   The normalizer bug is here: https://github.com/beluga-php/docker-php-api/blob/a287d09bb7164da7cef5b1e652550a15cb739d58/src/Normalizer/ContainerConfigExposedPortsItemNormalizer.php#L57

   Here is also a Claude summary in case someone wants to read that:

     Bug: Images without EXPOSE don't get port bindings
   
     When using withExposedPorts() on images that don't have EXPOSE in their Dockerfile, port bindings don't work.
   
     Root cause: ContainerConfigExposedPortsItem (extends ArrayObject) serializes to [] when empty, but Docker expects {}. The ContainerConfigExposedPortsItemNormalizer::normalize() returns an empty array which
     JSON-encodes as [].
   
     Workaround: Set a dummy key in the item:
     $item = new ContainerConfigExposedPortsItem();
     $item['_'] = true;  // Forces serialization to {"_":true} instead of []
   
     Fix: The normalizer should return new \stdClass() for empty items to produce {} in JSON.