Code Monkey home page Code Monkey logo

docker-qpid-dispatch's Introduction

Build Status

Apache Qpid Dispatch Docker image

Docker image for Apache Qpid Dispatch router. The image is based on CentOS 7.

Using the image

The Docker image can be configured using following environment variables:

  • QDROUTERD_HOME defines the main directory where all data are stored. By default /var/lib/qdrouterd/
  • QDROUTERD_ID defines the ID of the Dispatch router instance. If not specified, it will be randomly generated.
  • QDROUTERD_WORKER_THREADS defines the number of worker threads used by the router. By default 4 threads are used.
  • QDROUTERD_LISTENER_LINK_CAPACITY defines the detaul link capacity which will be configured for all listeners. By default is set to 1000
  • QDROUTERD_LOG_LEVEL defines the default log level which will be used. By default info+.
  • QDROUTERD_CONFIG_FILE defines the location of the main configuration file. By default $QDROUTERD_HOME/etc/qdrouterd.conf
  • QDROUTERD_CONFIG_OPTIONS allows user to pass the complete content of the configuration file which should be used. If specified, the configuration file will not be generated by the image it self.
  • QDROUTERD_CONFIG_INSET allows to pass some additional configuration into the qdrouterd.conf file. The content of this variable will be simply added into the generated configuration file.

SSL configuration

  • QDROUTERD_SSL_DB_DIR defines the directory where all SSL related files are stored. By default $QDROUTERD_HOME/etc/ssl
  • QDROUTERD_SSL_SERVER_PUBLIC_KEY contains the public key of router's own certificate.
  • QDROUTERD_SSL_SERVER_PRIVATE_KEY contains the private key of router's own certificate.
  • QDROUTERD_SSL_DB_PASSWORD should contain the password to the private key (in case it is needed).
  • QDROUTERD_SSL_CERT_DB should contain the database of clients certificates (public keys) which will be used for client authentication.
  • QDROUTERD_SSL_TRUSTED_CERTS list of supported CAs which will be presented to the SSL clients. If not specified, QDROUTERD_SSL_CERT_DB will be used.
  • QDROUTERD_SSL_AUTHENTICATE_PEER defines whether peer authentication is required or not.
  • QDROUTERD_SSL_UID_FORMAT configures the mechanism which is used to create the username based on the certificate (e.g. based on CN, SHA signature etc.). For more details about the different options visit the Qpid Dispatch documentation.
  • QDROUTERD_DISPLAY_NAME_MAPPING configures the display name mapping file, which maps SSL certificates against usernames based on a JSON file with mapping. This variable should contain the JSON mapping as text. Do not use at the same time QDROUTERD_DISPLAY_NAME_FILE.
  • QDROUTERD_DISPLAY_NAME_FILE configures the display name mapping file, which maps SSL certificates against usernames based on a JSON file with mapping. This variable should contain the path to the mapping file, which has to be included into the image on external volume. Do not use at the same time QDROUTERD_DISPLAY_NAME_MAPPING.

SASL configuration

  • QDROUTERD_SASL_DB defines the path to the SASL database containing the usernames and passwords. By default $QDROUTERD_HOME/etc/sasl/qdrouterd.sasldb
  • QDROUTERD_ADMIN_USERNAME specifies the username of the admin user which will be added to the ŚASL database.
  • QDROUTERD_ADMIN_PASSWORD specifies the password of the admin user.
  • QDROUTERD_SASL_CONFIG_DIR defines the directory where the SASL configuration will be stored, By default $QDROUTERD_HOME/etc/sasl/.
  • QDROUTERD_SASL_CONFIG_NAME defines the SASL configuration name, which is used to name the SASL configuration file. By default qdrouterd.

Policy configuration

  • QDROUTERD_MAX_CONNECTIONS defines the maximal number of connections per router. By default 65535 (max integer).
  • QDROUTERD_POLICY_DIR defines the directory where security policies will be stored. By default $QDROUTERD_HOME/etc/auth-policy/.
  • QDROUTERD_POLICY_RULES might contain one set of policy rules in JSON format. The content of this variable will be placed into a file in the QDROUTERD_POLICY_DIR directory.

docker-qpid-dispatch's People

Contributors

scholzj avatar

Stargazers

avatar avatar avatar

Watchers

avatar avatar avatar avatar avatar

Forkers

omallassi jbride hguerrero lillisebe sdhxw09 slinkydeveloper

docker-qpid-dispatch's Issues

How do i start listening?

Hi, I'm trying to run this image using:

docker run -P scholzj/qpid-dispatch

just with the default configuration (like I do without docker), but I don't know why the server never start listening:

2020-02-17 17:54:47.712594 +0000 SERVER (warning) HTTP support is not available
2020-02-17 17:54:47.712614 +0000 SERVER (info) Container Name: NTY1ZmVjMjJjMDZkNTdhY2E4ODIxOGQ4
2020-02-17 17:54:47.712647 +0000 ROUTER (info) Router started in Standalone mode
2020-02-17 17:54:47.712652 +0000 ROUTER (info) Version: 1.9.0
2020-02-17 17:54:47.712828 +0000 ROUTER (info) Core module present but disabled: edge_router
2020-02-17 17:54:47.712842 +0000 ROUTER (info) Core module present but disabled: core_test_hooks
2020-02-17 17:54:47.712846 +0000 ROUTER (info) Core module present but disabled: edge_addr_tracking
2020-02-17 17:54:47.712850 +0000 ROUTER (info) Core module present but disabled: address_lookup_server
2020-02-17 17:54:47.712857 +0000 ROUTER (info) Core module enabled: address_lookup_client
2020-02-17 17:54:47.712861 +0000 ROUTER (info) Router Core thread running. 0/NTY1ZmVjMjJjMDZkNTdhY2E4ODIxOGQ4
2020-02-17 17:54:47.712866 +0000 ROUTER (info) In-process subscription M/$management
2020-02-17 17:54:47.720602 +0000 AGENT (info) Activating management agent on $_management_internal
2020-02-17 17:54:47.720674 +0000 ROUTER (info) In-process subscription L/$management
2020-02-17 17:54:47.720704 +0000 ROUTER (info) In-process subscription L/$_management_internal
2020-02-17 17:54:47.720940 +0000 POLICY (info) Policy configured maxConnections: 65535, policyDir: '',access rules enabled: 'false', use hostname patterns: 'false'
2020-02-17 17:54:47.721538 +0000 POLICY (info) Policy fallback defaultVhost is defined: '$default'
2020-02-17 17:54:47.721574 +0000 SERVER (notice) Operational, 4 Threads Running (process ID 1)

Without docker, I see:

% qdrouterd                                                                                                                                                                                 
2020-02-17 18:56:56.678003 +0100 SERVER (info) Container Name: Standalone_QI68_87Ab1I8euP
2020-02-17 18:56:56.678057 +0100 ROUTER (info) Router started in Standalone mode
2020-02-17 18:56:56.678061 +0100 ROUTER (info) Version: 1.9.0
2020-02-17 18:56:56.678250 +0100 ROUTER (info) Core module present but disabled: edge_router
2020-02-17 18:56:56.678282 +0100 ROUTER (info) Core module present but disabled: core_test_hooks
2020-02-17 18:56:56.678286 +0100 ROUTER (info) Core module present but disabled: edge_addr_tracking
2020-02-17 18:56:56.678288 +0100 ROUTER (info) Core module present but disabled: address_lookup_server
2020-02-17 18:56:56.678291 +0100 ROUTER (info) Core module enabled: address_lookup_client
2020-02-17 18:56:56.678294 +0100 ROUTER (info) Router Core thread running. 0/Standalone_QI68_87Ab1I8euP
2020-02-17 18:56:56.678297 +0100 ROUTER (info) In-process subscription M/$management
2020-02-17 18:56:56.682222 +0100 AGENT (info) Activating management agent on $_management_internal
2020-02-17 18:56:56.682293 +0100 ROUTER (info) In-process subscription L/$management
2020-02-17 18:56:56.682309 +0100 ROUTER (info) In-process subscription L/$_management_internal
2020-02-17 18:56:56.683207 +0100 POLICY (info) Policy configured maxConnections: 65535, policyDir: '',access rules enabled: 'false', use hostname patterns: 'false'
2020-02-17 18:56:56.683622 +0100 POLICY (info) Policy fallback defaultVhost is defined: '$default'
2020-02-17 18:56:56.683751 +0100 CONN_MGR (info) Configured Listener: 0.0.0.0:amqp proto=any, role=normal
2020-02-17 18:56:56.684239 +0100 CONN_MGR (info) Configured Listener: 0.0.0.0:8672 proto=any, role=normal, http
2020-02-17 18:56:56.684309 +0100 SERVER (info) HTTP server thread running
2020-02-17 18:56:56.684404 +0100 SERVER (notice) Listening for HTTP on 0.0.0.0:8672
2020-02-17 18:56:56.685597 +0100 SERVER (notice) Operational, 4 Threads Running (process ID 188996)
2020-02-17 18:56:56.685678 +0100 SERVER (notice) Listening on 0.0.0.0:amqp

Any ideas? I'm using the latest version of the image

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.