- Getting started
Openfire is a real time collaboration (RTC) server licensed under the Open Source Apache License. It uses the only widely adopted open protocol for instant messaging, XMPP (also called Jabber). Openfire is incredibly easy to setup and administer, but offers rock-solid security and performance.
If you find this image useful here's how you can help:
- Send a pull request with your awesome features and bug fixes
- Help users resolve their issues.
- Support the development of this image with a donation
Before reporting your issue please try updating Docker to the latest version and check if it resolves the issue. Refer to the Docker installation guide for instructions.
SELinux users should try disabling SELinux using the command
setenforce 0 to see if it resolves the issue.
If the above recommendations do not help then report your issue along with the following information:
- Output of the
docker runcommand or
docker-compose.ymlused to start the image. Mask out the sensitive bits.
- Please state if you are using Boot2Docker, VirtualBox, etc.
Automated builds of the image are available on Dockerhub and is the recommended method of installation.
Note: Builds are also available on Quay.io
Alternatively you can build the image yourself.
docker build -t sameersbn/openfire github.com/sameersbn/docker-openfire
Start Openfire using:
docker run --name openfire -d --restart=always \ --publish 9090:9090 --publish 5222:5222 --publish 7777:7777 \ --volume /srv/docker/openfire:/var/lib/openfire \ bunnyfu/openfire:4.0.3
Point your browser to http://localhost:9090 and follow the setup procedure to complete the installation. The Build A Free Jabber Server In 10 Minutes video by HAKK5 should help you with the configuration and also introduce you to some of its features.
For the Openfire to preserve its state across container shutdown and startup you should mount a volume at
The Quickstart command already mounts a volume for persistence.
SELinux users should update the security context of the host mountpoint so that it plays nicely with Docker:
mkdir -p /srv/docker/openfire chcon -Rt svirt_sandbox_file_t /srv/docker/openfire
To access the Openfire logs, located at
/var/log/openfire, you can use
docker exec. For example, if you want to tail the logs:
docker exec -it openfire tail -f /var/log/openfire/info.log
To upgrade to newer releases:
Download the updated Docker image:
docker pull bunnyfu/openfire:4.0.3
Stop the currently running image:
docker stop openfire
Remove the stopped container
docker rm -v openfire
Start the updated image
docker run -name openfire -d \ [OPTIONS] \ bunnyfu/openfire:4.0.3
For debugging and maintenance purposes you may want access the containers shell. If you are using Docker version
1.3.0 or higher you can access a running containers shell by starting
docker exec -it openfire bash
Hello, it's not openfire 4.0.3 when we download this images
Unable to find image 'bunnyfu/openfire:4.0.3' locally
Pulling repository docker.io/bunnyfu/openfire
docker: Tag 4.0.3 not found in repository docker.io/bunnyfu/openfire.
Is the tag 4.0.3 correct?
openfire 4.0.2 needs jre 8, not jre 7.