CODEWITHSUNDEEP
spring-bootdockerdocker-compose
BaDr Amer
BaDr Amer

Reputation: 910

Can't access spring boot app running inside docker container from localhost

I've been struggling for a couple of hours on this issue. I have the following setup:

Dockerfile

FROM openjdk:8-jdk-alpine
ARG JAR_FILE=target/ROOT.jar
COPY ${JAR_FILE} app.jar
ENTRYPOINT ["java","-jar","app.jar","--spring.profiles.active=dev"]
EXPOSE 8080

docker-compose.yml

version: '3'
services:
  app:
      container_name: app
      build:
         context: .
         dockerfile: Dockerfile
      restart: always
      links:
        - mysql-db
      depends_on:
        - mysql-db
      ports:
        - 8080:8080
      expose:
        - 8080
      networks:
        - spring-network
  mysql-db:
      restart: always
      container_name: mysql_db
      image: "mysql:8.0.19" 
      ports:
        - 3306:3306
      networks:
        - spring-network
      environment:
         MYSQL_ROOT_PASSWORD: 'password'
         MYSQL_DATABASE: 'db'
         MYSQL_USER: 'db-user'
         MYSQL_PASSWORD: 'password'
      volumes:
        - mysql-db:/var/lib/mysql
      command: --innodb-use-native-aio=0
      security_opt:
        - seccomp:unconfined
volumes:
  mysql-db:
networks:
    spring-network:
        driver: bridge

when I run the app using docker-compose up it works fine inside the container, but when I hit localhost:8080 on the browser I got

localhost unexpectedly closed the connection

Edit:

Upvotes: 0

Views: 3720

Answers (2)

BaDr Amer
BaDr Amer

Reputation: 910

After a few days, I figured out what was the issue. I was using an old jar file (which exposes the application on port 80 :/ ), all I did is generating a new build which exposes the app on 8080 mvn clean install then build the image docker-compose build and everything works fine now

Upvotes: 2

StefanE
StefanE

Reputation: 7630

Remove expose - it's for internal use between containers

Documentation for expose

Edit: You also have a brided network and you can only communicate between containers on the same bridged network as default.

Either just remove the network parts - this could cause containers being too exposed if this is a problem.

Or read about port forwarding here

Upvotes: 0

Related Questions