Navigation

    FusionAuth
    • Login
    • Search
    • Home
    • Categories
    • Recent
    • Popular
    • Pricing
    • Contact us
    • Docs
    1. Home
    2. Tags
    3. docker
    Log in to post
    • All categories
    • D

      UNSOLVED FusionAuth with Fly.io
      Q&A • docker docker-compose documentation developers postgres • • duke

      2
      0
      Votes
      2
      Posts
      298
      Views

      dan

      For future readers, @duke wrote up an entire article about this: https://medium.com/@osain/deploying-fusionauth-docker-on-fly-io-8fbeb0469556

    • dan

      UNSOLVED Want access to my docker logs
      Q&A • docker logs log files • • dan

      4
      0
      Votes
      4
      Posts
      466
      Views

      joshua

      @sullivan

      Thanks for the question. The reason that you are not seeing anything in this view is you need to have a docker logger set up. FusionAuth will write system logs to STDOUT. This output must be picked up by a logger in Docker (which can then be reviewed). By contrast, if you were running FusionAuth in a non-containerized environment, this view would show you current system logs.

      https://docs.docker.com/config/containers/logging/configure/

      Hope this helps!

      Thanks,
      Josh

    • dan

      ARM support
      Q&A • arm docker • • dan

      2
      0
      Votes
      2
      Posts
      265
      Views

      dan

      have you seen this https://github.com/jerryhopper/fusionauth-app-multiarch ?
      it's from community member @hopper-jerry and may meet your needs.

    • dan

      I want to send email from my docker image
      Q&A • email docker • • dan

      2
      1
      Votes
      2
      Posts
      817
      Views

      dan

      I end up using a docker image of mailcatcher.

      I use the default docker-compose.yml, but use this docker-compose.override.yml:

      version: '3' services: mailcatcher: image: yappabe/mailcatcher ports: - "1025:1025" - "1080:1080" networks: - mailcatcher search: image: docker.elastic.co/elasticsearch/elasticsearch:7.8.1 environment: cluster.name: fusionauth bootstrap.memory_lock: "true" discovery.type: single-node FUSIONAUTH_SEARCH_MEMORY: ${FUSIONAUTH_SEARCH_MEMORY} ES_JAVA_OPTS: ${ES_JAVA_OPTS} # Un-comment to access the search service directly # ports: # - 9200:9200 # - 9300:9300 networks: - search restart: unless-stopped ulimits: memlock: soft: -1 hard: -1 volumes: - es_data:/usr/share/elasticsearch/data fusionauth: depends_on: - search - mailcatcher environment: SEARCH_SERVERS: http://search:9200 SEARCH_TYPE: elasticsearch networks: - mailcatcher - search networks: search: driver: bridge mailcatcher: driver: bridge volumes: es_data:

      Then I configure the SMTP settings to use the hostname mailcatcher and the port 1025. I can then send email and view it in the mailcatcher interface, at localhost:1080.

      Here's the relevant dockerfile: https://github.com/yappabe/docker-mailcatcher/blob/master/Dockerfile

      Here's more about mailcatcher: https://mailcatcher.me/

    • X

      Can't connect to web interface.
      General Discussion • docker user management • • xan

      3
      0
      Votes
      3
      Posts
      689
      Views

      dan

      How much memory are you giving to the java process?

      You can also switch to the database search engine and see if removing ES resolves the issue. At that point it might be a resource issue.

      https://fusionauth.io/docs/v1/tech/tutorials/switch-search-engines/ has instructions on how to change these.

    • K

      fusionauth-example-asp-netcore: Malformed client_id
      Q&A • dotnet docker error jwt cookies • • kwatters

      3
      0
      Votes
      3
      Posts
      495
      Views

      dan

      That's great to hear, glad you figured it out!

    • dan

      How can I pull the latest docker image
      Q&A • docker docker-compose update image • • dan

      2
      0
      Votes
      2
      Posts
      1090
      Views

      dan

      The docker compose references the latest tag, but that tag is not dynamic, it is only the latest at a point in time.

      To ensure you have the most recent latest tag - you can always run this command: docker pull fusionauth/fusionauth-app:latest

      This is a common point of confusion, and there are lots of opinions on it as you might imagine. For your reading pleasure:

      https://vsupalov.com/docker-latest-tag/
      https://blog.container-solutions.com/docker-latest-confusion

    • dan

      Any way to modify the elasticsearch index?
      Q&A • configuration docker elasticsearch • • dan

      2
      0
      Votes
      2
      Posts
      320
      Views

      dan

      When you re-index, we delete our named index and rebuild it.

      You would probably be better off creating your own index.

    • dan

      How can you use kickstart with docker
      Q&A • docker kickstart • • dan

      2
      0
      Votes
      2
      Posts
      712
      Views

      dan

      Check out the official documentation on using Docker + Kickstart.

    • dan

      How can I make sure FusionAuth is running when I start it via docker-compose?
      Q&A • docker docker-compose troubleshooting • • dan

      3
      0
      Votes
      3
      Posts
      509
      Views

      C

      @dan said in How can I make sure FusionAuth is running when I start it via docker-compose?:

      It's not responding at the port 9011, like it should.
      Is there a way to test or ping the FusionAuth App to make sure its up and running other than using docker ps -a?

      Yes, there are several ways to test or ping the FusionAuth App to check if it's up and running without relying on the docker ps -a command. Here are a few alternative methods:

      Curl or wget: You can use the curl or wget command-line tools to send a request to the FusionAuth App's endpoint and check the response. For example, you can run curl http://localhost:9011 or wget http://localhost:9011 to send a GET request to the FusionAuth App running on port 9011. If you receive a valid response, it indicates that the app is up and running.

      Telnet: You can use the telnet command to establish a connection to the FusionAuth App's port and check if it's open and responsive. Run telnet localhost 9011 to attempt a connection to the FusionAuth App on port 9011. If the connection is successful, it means the app is running and accepting connections.

      Browser access: Simply open a web browser and enter the URL http://localhost:9011 to access the FusionAuth App. If the app is running correctly, you should be able to see the login or landing page.

      API client: If the FusionAuth App provides an API, you can use an API client like Postman or cURL to send a request to the API endpoints and verify if you receive the expected responses.

      These methods allow you to test the availability and responsiveness of the FusionAuth App without relying on the docker ps -a command or using Docker-specific tools.