Portainer Templates logo

Portainer Templates

Solr Solr

Container

Search Engine

Open-source enterprise search platform

Image details

Pulls: 355.3M
Architecture: amd64, arm64, arm/v7, ppc64le, s390x, riscv64, arm64/v8
Image size: 153 MB
Latest: 9.9.0-slim
User: library
Created: Oct 16, 2015
Updated: 11 days ago
Status: active

Configuration

Type
Container
Platform
linux
Image
solr:latest
Ports
8983/tcp
Volumes
/opt/solr/mydata

Template by portainer

Standalone Install

Select an install method, to see config/commands for deploying Solr

Installation method

Install on Portainer

Import all app templates into your Portainer instance, for easy 1-click deploys

  1. Ensure both Docker and Portainer are installed, and up-to-date
  2. Log into your Portainer web UI
  3. Under Settings → App Templates, paste the below URL
  4. Head to Home → App Templates, and the list of apps will show up
  5. Select Solr, fill in any config options, and hit Deploy

Template Import URL

https://raw.githubusercontent.com/Lissy93/portainer-templates/main/templates.json
Show Me demo

More install options in our documentation.

Quick reference

  • Maintained by: 
[the Apache Solr project](https://github.com/apache/solr)
  • Where to get help: 
[the Solr Community](https://solr.apache.org/community.html)

Supported tags and respective Dockerfile links






Quick reference (cont.)

  • Where to file issues: 
[The Solr Users mailing list](https://solr.apache.org/community.html#mailing-lists-chat)
[`amd64`](https://hub.docker.com/r/amd64/solr/), [`arm64v8`](https://hub.docker.com/r/arm64v8/solr/), [`ppc64le`](https://hub.docker.com/r/ppc64le/solr/), [`riscv64`](https://hub.docker.com/r/riscv64/solr/), [`s390x`](https://hub.docker.com/r/s390x/solr/)
  • Published image artifact details: 
[repo-info repo's `repos/solr/` directory](https://github.com/docker-library/repo-info/blob/master/repos/solr) ([history](https://github.com/docker-library/repo-info/commits/master/repos/solr))  
(image metadata, transfer size, etc)
  • Image updates: 
[official-images repo's `library/solr` label](https://github.com/docker-library/official-images/issues?q=label%3Alibrary%2Fsolr)  
[official-images repo's `library/solr` file](https://github.com/docker-library/official-images/blob/master/library/solr) ([history](https://github.com/docker-library/official-images/commits/master/library/solr))
  • Source of this description: 
[docs repo's `solr/` directory](https://github.com/docker-library/docs/tree/master/solr) ([history](https://github.com/docker-library/docs/commits/master/solr))

What is Solr?

Solr is the blazing-fast, open source, multi-modal search platform built on Apache Lucene. It powers full-text, vector, analytics, and geospatial search at many of the world's largest organizations. Other major features include Kubernetes integration, streaming, highlighting, faceting, and spellchecking.
Learn more on Apache Solr homepage and in the Apache Solr Reference Guide.
logo

How to use this Docker image

Full documentation can be found in the Solr Reference Guide's Docker section.
To run a single Solr server:
$ docker run -p 8983:8983 -t solr

Then with a web browser go to http://localhost:8983/ to see the Solr Admin Console.

About this repository

This repository is available on github.com/apache/solr-docker, but the image is built and maintained in the official Solr repo github.com/apache/solr.
Please direct any usage questions to the Solr users mailing list.

History

This project was started in 2015 by Martijn Koster in the github.com/docker-solr/docker-solr repository. In 2019, the maintainership and copyright was transferred to the Apache Solr project. Many thanks to Martijn for all your contributions over the years!

Image Variants

The solr images come in many flavors, each designed for a specific use case.

solr:<version>

This is the defacto image. If you are unsure about what your needs are, you probably want to use this one. It is designed to be used both as a throw away container (mount your source code and start the container to start your app), as well as the base to build other images off of.

solr:<version>-slim

This image does not contain the common packages contained in the default tag and only contains the minimal packages needed to run solr. Unless you are working in an environment where only the solr image will be deployed and you have space constraints, we highly recommend using the default image of this repository.

License

Solr is licensed under the Apache License, Version 2.0.
This repository is also licensed under the Apache License, Version 2.0.
Copyright 2015-2022 The Apache Software Foundation
Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.
As with all Docker images, these likely also contain other software which may be under other licenses (such as Bash, etc from the base distribution, along with any direct or indirect dependencies of the primary software being contained).
Some additional license information which was able to be auto-detected might be found in the repo-info repository's solr/ directory.
As for any pre-built image usage, it is the image user's responsibility to ensure that any use of this image complies with any relevant licenses for all software contained within.

Serve Solr on your own domain behind Caddy, Nginx or Traefik. Fill in your domain and copy the result. It's a starting point, some apps need their own base URL or extra headers set too.

Proxying solr.example.com to http://solr:8983

Add this to your Caddyfile

solr.example.com {
	reverse_proxy http://solr:8983
}

Check the logs first

Nine times out of ten the logs tell you exactly what went wrong.

  • In Portainer, go to Containers, click the container, then Logs. Or run docker logs <container>
  • Exit codes help too: 137 means killed, usually out of memory. 126 or 127 means the command inside the image is broken.

Published on a random port

This template exposes 8983/tcp without setting a host port, so Docker picks a random free one on every deploy.

  • Find it in the Ports column of Portainer's container list, or with docker port <container>

Image won't pull

Test the pull directly on the host: docker pull solr:latest

  • "manifest unknown" means the tag no longer exists. This template uses latest, so try pinning a specific version instead.
  • "toomanyrequests" is the Docker Hub rate limit. Log in with docker login to raise it.
  • "no space left on device" means a full disk. Reclaim space with docker system prune

"exec format error"

This means the image was built for a different CPU architecture than your server.

  • This image supports: amd64, arm64, arm/v7, ppc64le, s390x, riscv64, arm64/v8
  • Check yours with uname -m: x86_64 is amd64, aarch64 is arm64. Raspberry Pi and other ARM boards are the usual culprits.

Raise an issue

Found something which isn't working as it should? Here's how to report it.

A single container

Solr runs as one container, the simplest kind of app here. Just the one image to pull and nothing else wired up alongside it.

The app image

An image is the app packed up ready to go, everything Solr needs bundled into one download. This template pulls solr:latest, which Docker fetches once (about 153 MB) and then starts your own copy from.

Where the image comes from

Docker pulls its images from registries, public libraries of ready-built apps. Solr's comes from Docker Hub as one of its official, curated images.

Version tags

The bit after the colon in the image name is the version tag. Here it's latest, which always points at the newest build, so a redeploy can bump you to a newer release without you asking. Newest right now is 9.9.0-slim. Pin a specific tag if you would rather stay on one version.

Which machines it runs on

Every image is built for particular CPU types. This one ships for amd64, arm64, arm/v7, ppc64le, s390x, riscv64, arm64/v8, so it runs on both regular x86 servers and ARM boards like a Raspberry Pi.

Ports

A port is the door the app answers on. Here the app exposes a port but leaves the host side blank, so Docker picks a free one for you. It opens:

  • 8983, published on a random host port

Volumes

A volume is where Solr keeps its files so they survive an update or a restart. Without one, anything it saves would sit inside the container and vanish the moment it's recreated. This template mounts:

  • /opt/solr/mydata as a volume Docker manages for you

Networking

Nothing custom is set, so Solr sits on Docker's default bridge network: its own private space that reaches the outside world only through the ports it publishes.

Platform

The platform is linux, the kind of system the container is built to run on. Docker and Portainer handle this on a normal Linux server.

Portainer app templates

Zooming out, this whole page comes from a Portainer app template: a short recipe telling Portainer how to set Solr up. Add the template list to Portainer once, then deploying Solr is a click rather than a wall of config.