AWS Elastic Beanstalk deploying Docker with simple SpringBoot Eureka image failure

I’m new to AWS and Elastic Beanstalk. I’m trying to test a multi-container Docker deployment with a simple Spring Boot Docker image https://hub.docker.com/r/springcloud/eureka/ just to see something working for now.

I’m uploading a very simple Dockerrun.aws.json file to the Beanstalk console:

  • Managing docker containers with ansible - best practices
  • Packer Docker builder, not accepting -v foo:/bar
  • redis+elk stack using docker-compose
  • Cannot connect Npgsql to Postgres DB running on Docker
  • Cannot start mysql or mysqld_safe on ubuntu
  • 3 different applications and docker containers
  • {
      "AWSEBDockerrunVersion": 2,
      "containerDefinitions": [
        {
          "name": "eureka1",
          "image": "springcloud/eureka",
          "essential": true,
          "memory": 128,
          "portMappings": [
            {
              "hostPort": 80,
              "containerPort": 8761
            }
          ]
        }
      ]
    }
    

    The springcloud/eureka Docker image starts by default the server on port 8761, and I’m mapping the host’s port 80 to the container’s port 8761.

    So opening the application’s url (something like http://sample-env-1.xxx.eu-central-1.elasticbeanstalk.com/ ), it should display the Eureka server interface… It doesn’t. It just says “Unable to connect” standard browser page.

    The logs don’t appear to indicate an error… Or at least I can’t see any obvious error.

  • Can't register code-push
  • Docker tomcat editing configuration files through dockerfile
  • How to access ports in docker custom bridge networks
  • Access JMX inside docker container with mapped ports
  • Sporadic Robolectric test failures when running inside Docker container
  • Fluentd not getting the correct docker container name after rancher upgrade
  • One Solution collect form web for “AWS Elastic Beanstalk deploying Docker with simple SpringBoot Eureka image failure”

    Seems like I was putting the “memory” parameter to 128 which probably was not enough. Switching it to “memoryReservation”: 128 made it work.

    Docker will be the best open platform for developers and sysadmins to build, ship, and run distributed applications.