docker-library
/
docs
mirror of https://github.com/docker-library/docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Fix markdown formatting to satisfy Travis

This commit is contained in:
Tianon Gravi 2019-06-11 12:48:32 -07:00
parent bb6474163f
commit e12eed4aac
1 changed files with 7 additions and 16 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

23
neo4j/content.md
View File

@ -21,12 +21,10 @@ This binds two ports (`7474` and `7687`) for HTTP and Bolt access to the Neo4j A
By default, this requires you to login with `neo4j/neo4j` and change the password. You can, for development purposes, disable authentication by passing `--env=NEO4J_AUTH=none` to docker run. By default, this requires you to login with `neo4j/neo4j` and change the password. You can, for development purposes, disable authentication by passing `--env=NEO4J_AUTH=none` to docker run.
# Documentation # Documentation
For more examples and complete documentation please go to our manual [here](https://neo4j.com/docs/operations-manual/current/docker/introduction/). For more examples and complete documentation please go to our manual [here](https://neo4j.com/docs/operations-manual/current/docker/introduction/).
# Releases after 3.4.14 and 3.5.6 # Releases after 3.4.14 and 3.5.6
As of 11th June 2019 all new Neo4j Docker images will be released with a base image of debian-slim instead of alpine linux. This was prompted by [security concerns](https://github.com/docker-library/openjdk/issues/320), which caused the docker maintainers to pull the alpine images from the official `openjdk` images. As of 11th June 2019 all new Neo4j Docker images will be released with a base image of debian-slim instead of alpine linux. This was prompted by [security concerns](https://github.com/docker-library/openjdk/issues/320), which caused the docker maintainers to pull the alpine images from the official `openjdk` images.
@ -35,34 +33,27 @@ Older Neo4j images have already been released with `openjdk:8-jre-alpine` as the
In addition to the supported tags, we also have these legacy images of Neo4j available through docker hub: In addition to the supported tags, we also have these legacy images of Neo4j available through docker hub:
* `3.5.5`, `3.5.5-enterprise` and earlier patches - `3.5.5`, `3.5.5-enterprise` and earlier patches
* `3.4.13`, `3.4.13-enterprise` and earlier patches - `3.4.13`, `3.4.13-enterprise` and earlier patches
* `3.3`, `3.3-enterprise`, `3.3.9`, `3.3.9-enterprise` and earlier patches - `3.3`, `3.3-enterprise`, `3.3.9`, `3.3.9-enterprise` and earlier patches
* `3.2`, `3.2-enterprise`, `3.2.14`, `3.2.14-enterprise` and earlier patches - `3.2`, `3.2-enterprise`, `3.2.14`, `3.2.14-enterprise` and earlier patches
A complete list of all available Neo4j images can be found here:
https://github.com/neo4j/docker-neo4j-publish/tree/master
A complete list of all available Neo4j images can be found here: https://github.com/neo4j/docker-neo4j-publish/tree/master
## Migrating from Alpine Linux to Debian Slim ## Migrating from Alpine Linux to Debian Slim
If you have created a custom Dockerfile based off a `neo4j` image, the main change to be aware of is that debian uses the `aptitude` package manager instead of `apk`. If you have created a custom Dockerfile based off a `neo4j` image, the main change to be aware of is that debian uses the `aptitude` package manager instead of `apk`. In most cases you can just replace uses of `apk` with `apt`, but be aware that not all packages in `apk` may be available or have the same name.
In most cases you can just replace uses of `apk` with `apt`, but be aware that not all packages in `apk` may be available or have the same name.
Alpine Linux provide a more complete comparison on their documentation page: Alpine Linux provide a more complete comparison on their documentation page:
https://wiki.alpinelinux.org/wiki/Comparison_with_other_distros https://wiki.alpinelinux.org/wiki/Comparison_with_other_distros
## Changes to file permission requirements ## Changes to file permission requirements
Some users have [raised concerns](https://github.com/neo4j/docker-neo4j/issues/130) that the Neo4j image changes file permissions on the host machine. Some users have [raised concerns](https://github.com/neo4j/docker-neo4j/issues/130) that the Neo4j image changes file permissions on the host machine.
By default, Neo4j runs as the user `neo4j` who only exists in the container, not on the host. That means that it's hard to set up mount folders on the host which this new user has write permissions for. By default, Neo4j runs as the user `neo4j` who only exists in the container, not on the host. That means that it's hard to set up mount folders on the host which this new user has write permissions for. We have updated the error messaging with advice about how to fix file permission errors. We also introduced writability checks and reduced the amount of file permission changes the image will perform. This has been found to interfere with some Kubernetes setups, so is currently an opt-in feature.
We have updated the error messaging with advice about how to fix file permission errors. We also introduced writability checks and reduced the amount of file permission changes the image will perform. This has been found to interfere with some Kubernetes setups, so is currently an opt-in feature.
To enforce stricter file permissions checking you can pass this environment variable to the container: To enforce stricter file permissions checking you can pass this environment variable to the container:
`--env SECURE_FILE_PERMISSIONS=yes` `--env SECURE_FILE_PERMISSIONS=yes`