The openlibrary repository must be cloned with ssh and not https so that git submodules can be fetched correctly. See the Git Cheat Sheet for more, including how to fix this if you use git clone https://...
Windows users should see Fix line endings, symlinks, and git submodules.
Before attempting to build openlibrary using the Docker instructions below, please read through these opening notes about setting up Docker. If you encounter any errors, the following section may serve as a troubleshooting guide.
Linux users (including those using a VM), can install Docker Engine or Docker Desktop. Docker has an FAQ about the difference between the two. Windows and macOS users should use Docker Desktop as of early 2023.
- Docker Engine: https://docs.docker.com/engine/install/#server (tested with 19.*)
- Docker Desktop: https://docs.docker.com/get-docker/
As of early 2023, following the installation instructions on Docker's website will install either Docker Desktop, which includes Docker Compose v2, or docker-ce and docker-compose-plugin (Linux only), both of which obviate the need to install docker-compose v1 separately.
Further, Compose V1 will no longer be supported by the end of June 2023 and will be removed from Docker Desktop. These directions are written for Compose V2, hence the use of docker compose rather than docker-compose. docker compose is meant to be a drop-in replacement for docker-compose.
If for some reason one cannot use a current version of Docker that includes the Docker Compose plugin, it can be installed separately
Finally, as of this writing (early 2023), the docker-compose that comes with relatively recent Linux distributions (e.g. Ubuntu 22.04) still works if it is already installed.
Before continuing, ensure you can successfully run Docker's hello-world container.
docker run hello-world
The output should include a Hello from Docker! message that will confirm everything is working with Docker and you can continue.
If Docker is unable to pull the hello-world:latest image from Docker Hub, try disabling your VPN if one is installed.
Linux users, note the lack of sudo before docker run hello-world. See the Linux post-installation instructions if you see the following error:
docker: permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Post "http://%2Fvar%2Frun%2Fdocker.sock/v1.24/containers/create": dial unix /var/run/docker.sock: connect: permission denied.
See 'docker run --help'.
If you have not yet forked and cloned the openlibrary repository, please see Forking and Cloning the Open Library Repository.
Make sure you git clone openlibrary using ssh instead of https as git submodules (e.g. infogami and acs) may not fetch correctly otherwise. See Modifying a repository wrongly cloned with https if you cloned with https.
Windows users should see Fix line endings, symlinks, and git submodules. Skipping those steps will likely prevent the containers from coming up.
Please use Docker Desktop >= 4.3.0 and make sure that Docker Desktop Preferences General / Use Docker Compose V2 is checked so that it is no longer required to install Rosetta 2 to run Docker.
If you are experiencing issues building JS, you may need to increase the RAM available to Docker. The defaults of 2GB ram and 1GB Swap are not enough. We recommend requirements of 4GB ram and 2GB swap. This resolved the error message of Killed when running build-assets.
All commands are from the project root directory, where compose.yaml is (i.e. path/to/your/forked/and/cloned/openlibrary):
docker compose build
This can take from a few minutes to more than 15 on older hardware. If for some reason the build fails, it's worth running again, as sometimes downloads time out.
docker compose up # Ctrl-C to stop
docker compose up -d # or, start in detached (silent) modeYou will know the environment is done loading when the text stops furiously scrolling by and you see the following repeating every few seconds on the console:
infobase_1 | 172.19.0.5:45716 - - [16/Feb/2023 16:54:10] "HTTP/1.1 GET /openlibrary.org/log/2023-02-16:0" - 200 OK
infobase_1 | 172.19.0.5:45730 - - [16/Feb/2023 16:54:15] "HTTP/1.1 GET /openlibrary.org/log/2023-02-16:0" - 200 OK
infobase_1 | 172.19.0.5:41790 - - [16/Feb/2023 16:54:20] "HTTP/1.1 GET /openlibrary.org/log/2023-02-16:0" - 200 OK
At this point, visit http://localhost:8080 and you should see the Open Library banner image with "development version" emblazoned upon it to signify that it's running from your local development server. From here you can log in locally.
That's it for the Docker set up. You can read on for more about Docker, including addressing possible errors, how to gracefully shut down the Docker development environment. Or you can look at the "Contributing" or "Learning the Code" sections of the Getting Started guide for more on git, how to find a good first issue to work on, how to develop for the front end, etc.
"openlibrary-web-1 | exec docker/ol-web-start.sh: no such file or directory" OR "/usr/bin/env: 'python\r': No such file or directory"
These errors may appear in different containers or with different file names, but look for file-not-found type errors where \r is in the filename, or there's exec, a path that seems to exist, and a no such file or directory error, e.g. openlibrary-web-1 | exec docker/ol-web-start.sh: no such file or directory
The likely cause here is that text files were given CRLF line endings during cloning+checkout. See Fix line endings, symlinks, and git submodules.
Note: after fixing this error, be on the lookout for another error that will appear almost immediately after running docker compose up that mentions something about the role of openlibrary not existing. Read on for how to address that.
Look for errors that appear very soon after running docker compose up that come from the openlibrary-db-1 container when it first starts mentioning something about the role of openlibrary not existing.
In this case, try the steps in Fully Resetting Your Environment
Note: please update this README with the exact wording of the error if you run into it.
OSError: [Errno 12] Cannot allocate memory: could occur in conjunction with /openlibrary/openlibrary/core or any number of files. Simply try increasing free RAM or increasing swap/page file/virtual memory for your operating system.
The following should populate the target of the infogami symbolic link (i.e. vendor/infogami/):
cd path/to/your/cloned/openlibrary
git submodule init; git submodule sync; git submodule update
Windows users may need to see Fix line endings, symlinks, and git submodules.
Ensure you're running docker compose commands from within the local-openlibrary-dev-directory.
The full error is something like (line breaks added):
/openlibrary/openlibrary/templates/home/index.html: error in processing
template: ConnectionError: HTTPConnectionPool(host='solr', port=8983):
Max retries exceeded with url: /solr/openlibrary/select (Caused by
NameResolutionError("<urllib3.connection.HTTPConnection object at
0x77a95c4e7f90>: Failed to resolve 'solr' ([Errno -2] Name or service
not known)")) (falling back to default template)
The following should get everything running again:
docker compose down
docker container ls -a
# If you see any openlibrary container here, remove them with `docker rm -f NAME`
docker network ls
# If you see any open library networks here, remove them with `docker network rm NAME
docker compose up # or docker compose up -dIf you're curious and want to understand what happened, and why the above likely fixes it, first, verify the solr container is running (e.g. docker ps | grep solr, and then look for something like openlibrary-solr-1 that isn't solr-updater.) If the solr container isn't running, simply start it with docker compose up solr (or docker compose up -d solr) and that should fix it. If solr is running, verify too that you can also connect to solr at http://localhost:8983/solr/#/. If you can't, something else is likely wrong.
If the solr container is running and the error persists, one cause seems to be that the containers sometimes become disconnected from openlibrary_webnet (though this could happen with openlibrary_dbnet too). openlibrary-web-1/web should be connected to both openlibrary_webnet and openlibrary_dbnet, but when this problem occurs, instead only one is connected. E.g.:
docker container inspect --format '{{.NetworkSettings.Networks}}' openlibrary-web-1
# output: map[openlibrary_dbnet:0xc00037c1c0]Because you've read this far, you can now directly fix the problem without removing the containers and networks. Simply reconnect the container to the network:
docker network connect openlibrary_webnet openlibrary-web-1 # or `openlibrary_dbnet` as the case may be.
docker container inspect --format '{{.NetworkSettings.Networks}}' openlibrary-web-1
# output: map[openlibrary_dbnet:0xc00016c460 openlibrary_webnet:0xc00016c540]
No restart is required. If webnet no longer exists, recreating it should fix things: docker network create openlibrary_webnet.
To understand a bit more about what's going on here, there are docker networks configured in compose.yaml. The containers should be able to resolve one another based on the container names (e.g. web and solr), assuming compose.yaml has them on the same netork. For more, see Networking in Compose.
cd path/to/your/cloned/openlibrary
# stop the app (if started in detached mode)
docker compose down
# start specific service
docker compose up --no-deps -d solr
# remove all volumes (i.e. reset all databases); perform WHILE RUNNING
docker compose stop
docker compose rm -vThis exposes the following ports:
| Port | Service |
|---|---|
| 8080 | Open Library main site |
| 7000 | Infobase |
| 8983 | Solr |
| 7075 | Cover store |
For example, to access Solr admin, go to http://localhost:8983/solr/admin/
For changes to the frontend (JS, CSS, and HTML/Templetor templates), see the Frontend Guide.
Other changes:
- Editing pip packages? Rebuild the
homeservice:docker compose build home - Editing npm packages? Run
docker compose run --rm home npm install --no-audit(see #2032 for why) - Editing core dependencies? You will most likely need to do a full rebuild. This shouldn't happen too frequently. If you are making this sort of change, you will know exactly what you are doing ;) See Developing the Dockerfile.
See Docker's docs for more: https://docs.docker.com/compose/reference/overview
# Read a service's logs (replace `web` with service name)
docker compose logs web # Show all logs (onetime)
docker compose logs -f --tail=10 web # Show last 10 lines and follow
# Analyze a container
docker compose exec web bash # Launch terminal in `web` service
# Run tests
docker compose run --rm home make test
# Install Node.js modules (if you get an error running tests)
# Important: npm jobs need to be run inside the Docker environment.
docker compose run --rm home npm install --no-audit
# build JS/CSS assets:
docker compose run --rm home npm run build-assetsBeen away for a while? Are you getting strange errors you weren't getting before? Sometimes changes are made to the docker configs which could cause your local environment to break. To do a full reset of your docker environment so that you have the latest of everything:
# Stop the site
docker compose down
# Build the latest oldev image, without cache, whilst also pulling the latest olbase image from docker hub.
# This can take from a few minutes to more than 20 on older hardware.
docker compose build --pull --no-cache
# Remove any old containers/images
# If you use docker for other things, and have containers/images you don't want to lose, be careful with this. But you likely don't :)
docker container prune --filter label="com.docker.compose.project=openlibrary" --force
docker image prune --filter label="com.docker.compose.project=openlibrary" --force
# Remove volumes that might have outdated dependencies/code
docker volume rm openlibrary_ol-build openlibrary_ol-nodemodules openlibrary_ol-vendor
# Bring it back up again
docker compose up # or docker compose up -d
If you need to make changes to the dependencies in Dockerfile.olbase, rebuild it with:
docker build -t openlibrary/olbase:latest -f docker/Dockerfile.olbase . # 30+ min (Win10Home/Dec 2018)This image is automatically rebuilt on deploy by ol-home0 and is pushed to at https://hub.docker.com/r/openlibrary/olbase.
If you're making changes you think might affect Docker Hub, you can create a branch starting with docker-test, e.g. docker-test-py2py3 (no weird chars), to trigger a build in docker hub at e.g. openlibrary/olbase:docker-test-py2py3.
Pull the changes into your openlibrary repository: git pull
When pulling down new changes you will need to rebuild the JS/CSS assets:
# build JS/CSS assets:
docker compose run --rm home npm run build-assetsNote: This is only if you already have an existing docker image, this command is unnecessary the first time you build.
See Debugging and Performance Profiling for more information on how to attach a debugger when running in the Docker Container.
https://github.com/internetarchive/openlibrary/wiki/Deployment-Guide#ol-web1
# Launch a temporary container and run tests
docker compose run --rm home make test
# Run Open Library using a local copy of Infogami for development
docker compose down && \
docker compose -f compose.yaml -f compose.override.yaml -f compose.infogami-local.yaml up -d && \
docker compose logs -f --tail=10 web
# In your browser, navigate to http://localhost:8080
# To test Open Library on another version of Python, modify Dockerfile.olbase and then
# rebuild olbase (see above) and oldev (`docker compose build`)