🕷️ Crawler Inspector

URL Lookup

Direct Parameter Lookup

Raw Queries and Responses

1. Shard Calculation

Query:

Response:

Calculated Shard: 70 (from laksa169)

2. Crawled Status Check

Query:

curl -X POST \
  'http://laksa070.int.ahrefs:8124/' \
  -H 'Content-Type: text/plain' \
  -H 'X-ClickHouse-Database: crawler3' \
  -H 'Authorization: Basic YXBpOg==' \
  -d 'SELECT getAhrefsURLFromUnparsed(src_unparsed) AS found_url, ifNull(toUnixTimestamp(download_stamp), 0) AS crawl_time, ifNull(toUnixTimestamp(props_url_first_seen), 0) AS first_indexed_time, download_http_code AS http_code, src_unparsed AS src_unparsed, src_root_hash AS src_root_hash, history_drop_reason AS history_drop_reason, meta_title AS meta_title, meta_descriptions AS meta_descriptions, attrs_boilerpipe_text AS attrs_boilerpipe_text, attrs_markdown AS attrs_markdown, attrs_readable_markdown AS attrs_readable_markdown, meta_canonical AS meta_canonical FROM crawler3.page_info_local FINAL PREWHERE (src_root_hash, src_unparsed) IN ((getAhrefsRootHashFromUnparsed(getAhrefsUnparsedNoserviceFromURL(\'https://hub.docker.com/_/nextcloud/\')), getAhrefsUnparsedNoserviceFromURL(\'https://hub.docker.com/_/nextcloud/\'))) FORMAT JSONEachRow'

Response:

{"found_url":"https:\/\/hub.docker.com\/_\/nextcloud\/","crawl_time":1775470900,"first_indexed_time":1483588023,"http_code":200,"src_unparsed":"com,docker!hub,\/_\/nextcloud\/ s443","src_root_hash":"8914333203171518870","history_drop_reason":null,"meta_title":"nextcloud - Official Image | Docker Hub","meta_descriptions":["Nextcloud manual docker image"],"attrs_boilerpipe_text":"Note:\nthe description for this image is longer than the Hub length limit of 25000, so has been trimmed.  The full description can be found at\nhttps:\/\/github.com\/docker-library\/docs\/tree\/master\/nextcloud\/README.md\n⁠\n.  See also\ndocker\/hub-feedback#238\n⁠\nand\ndocker\/roadmap#475\n⁠\n.\nIMPORTANT NOTE\n⚠️⚠️⚠️ This image is maintained by community volunteers and designed for expert use. For quick and easy deployment that supports the full set of Nextcloud Hub features, use the\nNextcloud All-in-One docker container\n⁠\nmaintained by Nextcloud GmbH.\nQuick reference\nMaintained by\n:\nthe Nextcloud community\n⁠\nWhere to get help\n:\nthe Docker Community Slack\n⁠\n,\nServer Fault\n⁠\n,\nUnix & Linux\n⁠\n, or\nStack Overflow\n⁠\nSupported tags and respective\nDockerfile\nlinks\n32.0.8-apache\n,\n32.0-apache\n,\n32-apache\n,\nstable-apache\n,\nproduction-apache\n,\n32.0.8\n,\n32.0\n,\n32\n,\nstable\n,\nproduction\n⁠\n32.0.8-fpm\n,\n32.0-fpm\n,\n32-fpm\n,\nstable-fpm\n,\nproduction-fpm\n⁠\n32.0.8-fpm-alpine\n,\n32.0-fpm-alpine\n,\n32-fpm-alpine\n,\nstable-fpm-alpine\n,\nproduction-fpm-alpine\n⁠\n33.0.2-apache\n,\n33.0-apache\n,\n33-apache\n,\napache\n,\n33.0.2\n,\n33.0\n,\n33\n,\nlatest\n⁠\n33.0.2-fpm\n,\n33.0-fpm\n,\n33-fpm\n,\nfpm\n⁠\n33.0.2-fpm-alpine\n,\n33.0-fpm-alpine\n,\n33-fpm-alpine\n,\nfpm-alpine\n⁠\nQuick reference (cont.)\nWhere to file issues\n:\nhttps:\/\/github.com\/nextcloud\/docker\/issues\n⁠\nSupported architectures\n: (\nmore info\n⁠\n)\namd64\n,\narm32v5\n,\narm32v6\n,\narm32v7\n,\narm64v8\n,\ni386\n,\nppc64le\n,\nriscv64\n,\ns390x\nPublished image artifact details\n:\nrepo-info repo's\nrepos\/nextcloud\/\ndirectory\n⁠\n(\nhistory\n⁠\n)\n(image metadata, transfer size, etc)\nImage updates\n:\nofficial-images repo's\nlibrary\/nextcloud\nlabel\n⁠\nofficial-images repo's\nlibrary\/nextcloud\nfile\n⁠\n(\nhistory\n⁠\n)\nSource of this description\n:\ndocs repo's\nnextcloud\/\ndirectory\n⁠\n(\nhistory\n⁠\n)\nWhat is Nextcloud?\nA safe home for all your data. Access & share your files, calendars, contacts, mail & more from any device, on your terms.\nThis Docker micro-service image is developed and maintained by the Nextcloud community. Nextcloud GmbH does not offer support for this Docker image. When you are looking to get professional support, you can become an\nenterprise\n⁠\ncustomer or use\nAIO\n⁠\n.\nHow to use this image\nThis image is designed to be used in a micro-service environment. There are two versions of the image you can choose from.\nThe\napache\ntag contains a full Nextcloud installation including an apache web server. It is designed to be easy to use and gets you running pretty fast. This is also the default for the\nlatest\ntag and version tags that are not further specified.\nThe second option is a\nfpm\ncontainer. It is based on the\nphp-fpm\nimage and runs a fastCGI-Process that serves your Nextcloud page. To use this image it must be combined with any webserver that can proxy the http requests to the FastCGI-port of the container.\nUsing the apache image\nThe apache image contains a webserver and exposes port 80. To start the container type:\n$\ndocker run -d -p 8080:80 nextcloud\nNow you can access Nextcloud at\nhttp:\/\/localhost:8080\/\n⁠\nfrom your host system.\nUsing the fpm image\nTo use the fpm image, you need an additional web server, such as\nnginx\n⁠\n, that can proxy http-request to the fpm-port of the container. For fpm connection this container exposes port 9000. In most cases, you might want to use another container or your host as proxy. If you use your host you can address your Nextcloud container directly on port 9000. If you use another container, make sure that you add them to the same docker network (via\ndocker run --network <NAME> ...\nor a\ncompose.yaml\nfile). In both cases you don't want to map the fpm port to your host.\n$\ndocker run -d nextcloud:fpm\nAs the fastCGI-Process is not capable of serving static files (style sheets, images, ...), the webserver needs access to these files. This can be achieved with the\nvolumes-from\noption. You can find more information in the Docker Compose section.\nUsing an external database\nBy default, this container uses SQLite for data storage but the Nextcloud setup wizard (appears on first run) allows connecting to an existing MySQL\/MariaDB or PostgreSQL database. You can also link a database container, e. g.\n--link my-mysql:mysql\n, and then use\nmysql\nas the database host on setup. More info is in the Docker Compose section.\nPersistent data\nThe Nextcloud installation and all data beyond what lives in the database (file uploads, etc.) are stored in the\nunnamed docker volume\n⁠\nvolume\n\/var\/www\/html\n. The docker daemon will store that data within the docker directory\n\/var\/lib\/docker\/volumes\/...\n. That means your data is saved even if the container crashes, is stopped or deleted.\nA named Docker volume or a mounted host directory should be used for upgrades and backups. To achieve this, you need one volume for your database container and one for Nextcloud.\nNextcloud:\n\/var\/www\/html\/\nfolder where all Nextcloud data lives\n$\ndocker run -d \\\n-v nextcloud:\/var\/www\/html \\\nnextcloud\nDatabase:\n\/var\/lib\/mysql\nMySQL \/ MariaDB Data\n\/var\/lib\/postgresql\/data\nPostgreSQL Data\n$\ndocker run -d \\\n-v db:\/var\/lib\/mysql \\\nmariadb:10.6\nAdditional volumes\nIf you want to get fine grained access to your individual files, you can mount additional volumes for data, config, your theme and custom apps. The\ndata\n,\nconfig\nfiles are stored in respective subfolders inside\n\/var\/www\/html\/\n. The apps are split into core\napps\n(which are shipped with Nextcloud and you don't need to take care of) and a\ncustom_apps\nfolder. If you use a custom theme it would go into the\nthemes\nsubfolder.\nOverview of the folders that can be mounted as volumes:\n\/var\/www\/html\nMain folder, needed for updating\n\/var\/www\/html\/custom_apps\ninstalled \/ modified apps\n\/var\/www\/html\/config\nlocal configuration\n\/var\/www\/html\/data\nthe actual data of your Nextcloud\n\/var\/www\/html\/themes\/<YOUR_CUSTOM_THEME>\ntheming\/branding\nIf you want to use named volumes for all of these, it would look like this:\n$\ndocker run -d \\\n-v nextcloud:\/var\/www\/html \\\n-v apps:\/var\/www\/html\/custom_apps \\\n-v config:\/var\/www\/html\/config \\\n-v data:\/var\/www\/html\/data \\\n-v theme:\/var\/www\/html\/themes\/<YOUR_CUSTOM_THEME> \\\nnextcloud\nCustom volumes\nIf mounting additional volumes under\n\/var\/www\/html\n, you should consider:\nConfirming that\nupgrade.exclude\n⁠\ncontains the files and folders that should persist during installation and upgrades; or\nMounting storage volumes to locations outside of\n\/var\/www\/html\n.\nYou should note that data inside the main folder (\n\/var\/www\/html\n) will be overridden\/removed during installation and upgrades, unless listed in\nupgrade.exclude\n⁠\n. The additional volumes officially supported are already in that list, but custom volumes will need to be added by you. We suggest mounting custom storage volumes outside of\n\/var\/www\/html\nand if possible read-only so that making this adjustment is unnecessary. If you must do so, however, you may build a custom image with a modified\n\/upgrade.exclude\nfile that incorporates your custom volume(s).\nUsing the Nextcloud command-line interface\nTo use the\nNextcloud command-line interface\n⁠\n(aka.\nocc\ncommand):\n$\ndocker\nexec\n--user www-data CONTAINER_ID php occ\nor for\ndocker compose\n:\n$\ndocker compose\nexec\n--user www-data app php occ\nAuto configuration via environment variables\nThe Nextcloud image supports auto configuration via environment variables. You can preconfigure everything that is asked on the install page on first run. To enable auto configuration, set your database connection via the following environment variables. You must specify all of the environment variables for a given database or the database environment variables defaults to SQLITE. ONLY use one database type!\nSQLite\n:\nSQLITE_DATABASE\nName of the database using sqlite\nMYSQL\/MariaDB\n:\nMYSQL_DATABASE\nName of the database using mysql \/ mariadb.\nMYSQL_USER\nUsername for the database using mysql \/ mariadb.\nMYSQL_PASSWORD\nPassword for the database user using mysql \/ mariadb.\nMYSQL_HOST\nHostname of the database server using mysql \/ mariadb.\nPostgreSQL\n:\nPOSTGRES_DB\nName of the database using postgres.\nPOSTGRES_USER\nUsername for the database using postgres.\nPOSTGRES_PASSWORD\nPassword for the database user using postgres.\nPOSTGRES_HOST\nHostname of the database server using postgres.\nAs an alternative to passing sensitive information via environment variables,\n_FILE\nmay be appended to the previously listed environment variables, causing the initialization script to load the values for those variables from files present in the container. See\nDocker secrets\nsection below.\nIf you set any group of values (i.e. all of\nMYSQL_DATABASE\n,\nMYSQL_USER\n,\nMYSQL_PASSWORD\n,\nMYSQL_HOST\n), they will not be asked in the install page on first run. With a complete configuration by using all variables for your database type, you can additionally configure your Nextcloud instance by setting admin user and password (only works if you set both):\nNEXTCLOUD_ADMIN_USER\nName of the Nextcloud admin user.\nNEXTCLOUD_ADMIN_PASSWORD\nPassword for the Nextcloud admin user.\nIf you want, you can set the data directory, otherwise default value will be used.\nNEXTCLOUD_DATA_DIR\n(default:\n\/var\/www\/html\/data\n) Configures the data directory where nextcloud stores all files from the users.\nOne or more trusted domains can be set through environment variable, too. They will be added to the configuration after install.\nNEXTCLOUD_TRUSTED_DOMAINS\n(not set by default) Optional space-separated list of domains\nThe install and update script is only triggered when a default command is used (\napache-foreground\nor\nphp-fpm\n). If you use a custom command you have to enable the install \/ update with\nNEXTCLOUD_UPDATE\n(default:\n0\n)\nYou might want to make sure the htaccess is up to date after each container update. Especially on multiple swarm nodes as any discrepancy will make your server unusable.\nNEXTCLOUD_INIT_HTACCESS\n(not set by default) Set it to true to enable run\nocc maintenance:update:htaccess\nafter container initialization.\nIf you want to use Redis you have to create a separate\nRedis\ncontainer in your setup \/ in your Compose file. To inform Nextcloud about the Redis container, pass in the following parameters:\nREDIS_HOST\n(not set by default) Name of Redis container\nREDIS_HOST_PORT\n(default:\n6379\n) Optional port for Redis, only use for external Redis servers that run on non-standard ports.\nREDIS_HOST_PASSWORD\n(not set by default) Redis password\nThe use of Redis is recommended to prevent file locking problems. See the examples for further instructions.\nTo use an external SMTP server, you have to provide the connection details. To configure Nextcloud to use SMTP add:\nSMTP_HOST\n(not set by default): The hostname of the SMTP server.\nSMTP_SECURE\n(empty by default): Set to\nssl\nto use SSL, or\ntls\nto use STARTTLS.\nSMTP_PORT\n(default:\n465\nfor SSL and\n25\nfor non-secure connections): Optional port for the SMTP connection. Use\n587\nfor an alternative port for STARTTLS.\nSMTP_AUTHTYPE\n(default:\nLOGIN\n): The method used for authentication. Use\nPLAIN\nif no authentication is required.\nSMTP_NAME\n(empty by default): The username for the authentication.\nSMTP_PASSWORD\n(empty by default): The password for the authentication.\nMAIL_FROM_ADDRESS\n(not set by default): Set the local-part for the 'from' field in the emails sent by Nextcloud.\nMAIL_DOMAIN\n(not set by default): Set a different domain for the emails than the domain where Nextcloud is installed.\nAt least\nSMTP_HOST\n,\nMAIL_FROM_ADDRESS\nand\nMAIL_DOMAIN\nmust be set for the configurations to be applied.\nCheck the\nNextcloud documentation\n⁠\nfor other values to configure SMTP.\nTo use an external S3 compatible object store as primary storage, set the following variables:\nOBJECTSTORE_S3_BUCKET\n: The name of the bucket that Nextcloud should store the data in\nOBJECTSTORE_S3_REGION\n: The region that the S3 bucket resides in\nOBJECTSTORE_S3_HOST\n: The hostname of the object storage server\nOBJECTSTORE_S3_PORT\n: The port that the object storage server is being served over\nOBJECTSTORE_S3_KEY\n: AWS style access key\nOBJECTSTORE_S3_SECRET\n: AWS style secret access key\nOBJECTSTORE_S3_STORAGE_CLASS\n: The storage class to use when adding objects to the bucket\nOBJECTSTORE_S3_SSL\n(default:\ntrue\n): Whether or not SSL\/TLS should be used to communicate with object storage server\nOBJECTSTORE_S3_USEPATH_STYLE\n(default:\nfalse\n): Not required for AWS S3\nOBJECTSTORE_S3_LEGACYAUTH\n(default:\nfalse\n): Not required for AWS S3\nOBJECTSTORE_S3_OBJECT_PREFIX\n(default:\nurn:oid:\n): Prefix to prepend to the fileid\nOBJECTSTORE_S3_AUTOCREATE\n(default:\ntrue\n): Create the container if it does not exist\nOBJECTSTORE_S3_SSE_C_KEY\n(not set by default): Base64 encoded key with a maximum length of 32 bytes for server side encryption (SSE-C)\nCheck the\nNextcloud documentation\n⁠\nfor more information.\nTo use an external OpenStack Swift object store as primary storage, set the following variables:\nOBJECTSTORE_SWIFT_URL\n: The Swift identity (Keystone) endpoint\nOBJECTSTORE_SWIFT_AUTOCREATE\n(default:\nfalse\n): Whether or not Nextcloud should automatically create the Swift container\nOBJECTSTORE_SWIFT_USER_NAME\n: Swift username\nOBJECTSTORE_SWIFT_USER_PASSWORD\n: Swift user password\nOBJECTSTORE_SWIFT_USER_DOMAIN\n(default:\nDefault\n): Swift user domain\nOBJECTSTORE_SWIFT_PROJECT_NAME\n: OpenStack project name\nOBJECTSTORE_SWIFT_PROJECT_DOMAIN\n(default:\nDefault\n): OpenStack project domain\nOBJECTSTORE_SWIFT_SERVICE_NAME\n(default:\nswift\n): Swift service name\nOBJECTSTORE_SWIFT_REGION\n: Swift endpoint region\nOBJECTSTORE_SWIFT_CONTAINER_NAME\n: Swift container (bucket) that Nextcloud should store the data in\nCheck the\nNextcloud documentation\n⁠\nfor more information.\nTo customize other PHP limits you can simply change the following variables:\nPHP_MEMORY_LIMIT\n(default\n512M\n) This sets the maximum amount of memory in bytes that a script is allowed to allocate. This is meant to help prevent poorly written scripts from eating up all available memory but it can prevent normal operation if set too tight.\nPHP_UPLOAD_LIMIT\n(default\n512M\n) This sets the upload limit (\npost_max_size\nand\nupload_max_filesize\n) for big files. Note that you may have to change other limits depending on your client, webserver or operating system. Check the\nNextcloud documentation\n⁠\nfor more information.\nTo customize Apache max file upload limit you can change the following variable:\nAPACHE_BODY_LIMIT\n(default\n1073741824\n[1GiB]) This restricts the total size of the HTTP request body sent from the client. It specifies the number of\nbytes\nthat are allowed in a request body. A value of\n0\nmeans\nunlimited\n. Check the\nNextcloud documentation\n⁠\nfor more information.\nAuto configuration via hook folders\nThere are 5 hooks\npre-installation\nExecuted before the Nextcloud is installed\/initiated\npost-installation\nExecuted after the Nextcloud is installed\/initiated\npre-upgrade\nExecuted before the Nextcloud is upgraded\npost-upgrade\nExecuted after the Nextcloud is upgraded\nbefore-starting\nExecuted before the Nextcloud starts\nTo use the hooks triggered by the\nentrypoint\nscript, either\nAdded your script(s) to the individual of the hook folder(s), which are located at the path\n\/docker-entrypoint-hooks.d\nin the container\nUse volume(s) if you want to use script from the host system inside the container, see example.\nNote:\nOnly the script(s) located in a hook folder (not sub-folders), ending with\n.sh\nand marked as executable, will be executed.\nExample:\nMount using volumes\n...\napp:\nimage:\nnextcloud:stable\nvolumes:\n-\n.\/app-hooks\/pre-installation:\/docker-entrypoint-hooks.d\/pre-installation\n-\n.\/app-hooks\/post-installation:\/docker-entrypoint-hooks.d\/post-installation\n-\n.\/app-hooks\/pre-upgrade:\/docker-entrypoint-hooks.d\/pre-upgrade\n-\n.\/app-hooks\/post-upgrade:\/docker-entrypoint-hooks.d\/post-upgrade\n-\n.\/app-hooks\/before-starting:\/docker-entrypoint-hooks.d\/before-starting\n...\nUsing the apache image behind a reverse proxy and auto configure server host and protocol\nThe apache image will replace the remote addr (IP address visible to Nextcloud) with the IP address from\nX-Real-IP\nif the request is coming from a proxy in\n10.0.0.0\/8\n,\n172.16.0.0\/12\nor\n192.168.0.0\/16\nby default. If you want Nextcloud to pick up the server host (\nHTTP_X_FORWARDED_HOST\n), protocol (\nHTTP_X_FORWARDED_PROTO\n) and client IP (\nHTTP_X_FORWARDED_FOR\n) from a trusted proxy, then disable rewrite IP and add the reverse proxy's IP address to\nTRUSTED_PROXIES\n.\nAPACHE_DISABLE_REWRITE_IP\n(not set by default): Set to 1 to disable rewrite IP.\nTRUSTED_PROXIES\n(empty by default): A space-separated list of trusted proxies. CIDR notation is supported for IPv4.\nIf the\nTRUSTED_PROXIES\napproach does not work for you, try using fixed values for overwrite parameters.\nOVERWRITEHOST\n(empty by default): Set the hostname of the proxy. Can also specify a port.\nOVERWRITEPROTOCOL\n(empty by default): Set the protocol of the proxy, http or https.\nOVERWRITECLIURL\n(empty by default): Set the cli url of the proxy (e.g.\nhttps:\/\/mydnsname.example.com\n⁠\n)\nOVERWRITEWEBROOT\n(empty by default): Set the absolute path of the proxy.\nOVERWRITECONDADDR\n(empty by default): Regex to overwrite the values dependent on the remote address.\nCheck the\nNexcloud documentation\n⁠\nfor more details.\nKeep in mind that once set, removing these environment variables won't remove these values from the configuration file, due to how Nextcloud merges configuration files together.\nRunning this image with Docker Compose\nThe easiest way to get a fully featured and functional setup is using a\ncompose.yaml\nfile. There are too many different possibilities to setup your system, so here are only some examples of what you have to look for.\nAt first, make sure you have chosen the right base image (fpm or apache) and added features you wanted (see below). In every case, you would want to add a database container and docker volumes to get easy access to your persistent data. When you want to have your server reachable from the internet, adding HTTPS-encryption is mandatory! See below for more information.\nBase version - apache\nThis version will use the apache image and add a mariaDB container. The volumes are set to keep your data persistent. This setup provides\nno ssl encryption\nand is intended to run behind a proxy.\nMake sure to pass in values for\nMYSQL_ROOT_PASSWORD\nand\nMYSQL_PASSWORD\nvariables before you run this setup.\nvolumes:\nnextcloud:\ndb:\nservices:\ndb:\nimage:\nmariadb:10.6\nrestart:\nalways\ncommand:\n--transaction-isolation=READ-COMMITTED\n--log-bin=binlog\n--binlog-format=ROW\nvolumes:\n-\ndb:\/var\/lib\/mysql\nenvironment:\n-\nMYSQL_ROOT_PASSWORD=\n-\nMYSQL_PASSWORD=\n-\nMYSQL_DATABASE=nextcloud\n-\nMYSQL_USER=nextcloud\napp:\nimage:\nnextcloud\nrestart:\nalways\nports:\n-\n8080\n:80\nlinks:\n-\ndb\nvolumes:\n-\nnextcloud:\/var\/www\/html\nenvironment:\n-\nMYSQL_PASSWORD=\n-\nMYSQL_DATABASE=nextcloud\n-\nMYSQL_USER=nextcloud\n-\nMYSQL_HOST=db\nThen run\ndocker compose up -d\n, now you can access Nextcloud at\nhttp:\/\/localhost:8080\/\n⁠\nfrom your host system.\nBase version - FPM\nWhen using the FPM image, you need another container that acts as web server on port 80 and proxies the requests to the Nextcloud container. In this example a simple nginx container is combined with the Nextcloud-fpm image and a MariaDB database container. The data is stored in docker volumes. The nginx container also needs access to static files from your Nextcloud installation. It gets access to all the volumes mounted to Nextcloud via the\nvolumes_from\noption. The configuration for nginx is stored in the configuration file\nnginx.conf\n, that is mounted into the container. An example can be found in the examples section\nhere\n⁠\n.\nAs this setup does\nnot include encryption\n, it should be run behind a proxy.\nMake sure to pass in values for\nMYSQL_ROOT_PASSWORD\nand\nMYSQL_PASSWORD\nvariables before you run this setup.\nvolumes:\nnextcloud:\ndb:\nservices:\ndb:\nimage:\nmariadb:10.6\nrestart:\nalways\ncommand:\n--transaction-isolation=READ-COMMITTED\n--log-bin=binlog\n--binlog-format=ROW\nvolumes:\n-\ndb:\/var\/lib\/mysql\nenvironment:\n-\nMYSQL_ROOT_PASSWORD=\n-\nMYSQL_PASSWORD=\n-\nMYSQL_DATABASE=nextcloud\n-\nMYSQL_USER=nextcloud\n...\n**Note:**\nthe\ndescription\nfor\nthis\nimage\nis\nlonger\nthan\nthe\nHub\nlength\nlimit\nof\n25000\n,\nso\nhas\nbeen\ntrimmed.\nThe\nfull\ndescription\ncan\nbe\nfound\nat\n[\nhttps:\/\/github.com\/docker-library\/docs\/tree\/master\/nextcloud\/README.md\n]\n(https:\/\/github.com\/docker-library\/docs\/tree\/master\/nextcloud\/README.md).\nSee\nalso\n[\ndocker\/hub-feedback#238\n]\n(https:\/\/github.com\/docker\/hub-feedback\/issues\/238)\nand\n[\ndocker\/roadmap#475\n]\n(https:\/\/github.com\/docker\/roadmap\/issues\/475).","attrs_markdown":"Search Docker Hub\n\nCtrlK\n\nHelp\n\nBack\n\n[Documentation⁠](https:\/\/docs.docker.com\/docker-hub)\n\n[Forums⁠](https:\/\/forums.docker.com\/c\/docker-hub)\n\n[Contact support](https:\/\/hub.docker.com\/support\/contact)\n\n[System status⁠](https:\/\/www.dockerstatus.com\/)\n\nSystem theme\n\n[Sign in](https:\/\/hub.docker.com\/login)[Sign up](https:\/\/app.docker.com\/signup)\n\nBack\n\nBack\n\nHelp\n\nBack\n\n[Documentation⁠](https:\/\/docs.docker.com\/docker-hub)\n\n[Forums⁠](https:\/\/forums.docker.com\/c\/docker-hub)\n\n[Contact support](https:\/\/hub.docker.com\/support\/contact)\n\n[System status⁠](https:\/\/www.dockerstatus.com\/)\n\nSystem theme\n\nDocker Suite\n\n1. [Explore](https:\/\/hub.docker.com\/search)\n2. \/\n3. [Official Images](https:\/\/hub.docker.com\/search?badges=official)\n4. \/\n5. nextcloud\n\n## nextcloud\nDocker Official Image\n\n•\n\n1B+\n\n•\n\n**4\\.5K**\n\nNextcloud manual docker image\n\n[Content management system](https:\/\/hub.docker.com\/categories\/content-management-system)\n\n[Overview](https:\/\/hub.docker.com\/_\/nextcloud\/)[Tags](https:\/\/hub.docker.com\/_\/nextcloud\/tags)\n\n# nextcloud Docker official image overview\n**Note:** the description for this image is longer than the Hub length limit of 25000, so has been trimmed. The full description can be found at [https:\/\/github.com\/docker-library\/docs\/tree\/master\/nextcloud\/README.md⁠](https:\/\/github.com\/docker-library\/docs\/tree\/master\/nextcloud\/README.md). See also [docker\/hub-feedback\\#238⁠](https:\/\/github.com\/docker\/hub-feedback\/issues\/238) and [docker\/roadmap\\#475⁠](https:\/\/github.com\/docker\/roadmap\/issues\/475).\n\n### IMPORTANT NOTE\n⚠️⚠️⚠️ This image is maintained by community volunteers and designed for expert use. For quick and easy deployment that supports the full set of Nextcloud Hub features, use the [Nextcloud All-in-One docker container⁠](https:\/\/github.com\/nextcloud\/all-in-one#nextcloud-all-in-one) maintained by Nextcloud GmbH.\n\n### Quick reference\n- **Maintained by**:  \n   [the Nextcloud community⁠](https:\/\/github.com\/nextcloud\/docker)\n- **Where to get help**:  \n   [the Docker Community Slack⁠](https:\/\/dockr.ly\/comm-slack), [Server Fault⁠](https:\/\/serverfault.com\/help\/on-topic), [Unix & Linux⁠](https:\/\/unix.stackexchange.com\/help\/on-topic), or [Stack Overflow⁠](https:\/\/stackoverflow.com\/help\/on-topic)\n### Supported tags and respective `Dockerfile` links\n- [`32.0.8-apache`, `32.0-apache`, `32-apache`, `stable-apache`, `production-apache`, `32.0.8`, `32.0`, `32`, `stable`, `production`⁠](https:\/\/github.com\/nextcloud\/docker\/blob\/efa6ee645631d34047625a82dfddd083324628ef\/32\/apache\/Dockerfile)\n- [`32.0.8-fpm`, `32.0-fpm`, `32-fpm`, `stable-fpm`, `production-fpm`⁠](https:\/\/github.com\/nextcloud\/docker\/blob\/efa6ee645631d34047625a82dfddd083324628ef\/32\/fpm\/Dockerfile)\n- [`32.0.8-fpm-alpine`, `32.0-fpm-alpine`, `32-fpm-alpine`, `stable-fpm-alpine`, `production-fpm-alpine`⁠](https:\/\/github.com\/nextcloud\/docker\/blob\/efa6ee645631d34047625a82dfddd083324628ef\/32\/fpm-alpine\/Dockerfile)\n- [`33.0.2-apache`, `33.0-apache`, `33-apache`, `apache`, `33.0.2`, `33.0`, `33`, `latest`⁠](https:\/\/github.com\/nextcloud\/docker\/blob\/efa6ee645631d34047625a82dfddd083324628ef\/33\/apache\/Dockerfile)\n- [`33.0.2-fpm`, `33.0-fpm`, `33-fpm`, `fpm`⁠](https:\/\/github.com\/nextcloud\/docker\/blob\/efa6ee645631d34047625a82dfddd083324628ef\/33\/fpm\/Dockerfile)\n- [`33.0.2-fpm-alpine`, `33.0-fpm-alpine`, `33-fpm-alpine`, `fpm-alpine`⁠](https:\/\/github.com\/nextcloud\/docker\/blob\/efa6ee645631d34047625a82dfddd083324628ef\/33\/fpm-alpine\/Dockerfile)\n### Quick reference (cont.)\n- **Where to file issues**:  \n   [https:\/\/github.com\/nextcloud\/docker\/issues⁠](https:\/\/github.com\/nextcloud\/docker\/issues?q=)\n- **Supported architectures**: ([more info⁠](https:\/\/github.com\/docker-library\/official-images#architectures-other-than-amd64))  \n   [`amd64`](https:\/\/hub.docker.com\/r\/amd64\/nextcloud\/), [`arm32v5`](https:\/\/hub.docker.com\/r\/arm32v5\/nextcloud\/), [`arm32v6`](https:\/\/hub.docker.com\/r\/arm32v6\/nextcloud\/), [`arm32v7`](https:\/\/hub.docker.com\/r\/arm32v7\/nextcloud\/), [`arm64v8`](https:\/\/hub.docker.com\/r\/arm64v8\/nextcloud\/), [`i386`](https:\/\/hub.docker.com\/r\/i386\/nextcloud\/), [`ppc64le`](https:\/\/hub.docker.com\/r\/ppc64le\/nextcloud\/), [`riscv64`](https:\/\/hub.docker.com\/r\/riscv64\/nextcloud\/), [`s390x`](https:\/\/hub.docker.com\/r\/s390x\/nextcloud\/)\n- **Published image artifact details**:  \n   [repo-info repo's `repos\/nextcloud\/` directory⁠](https:\/\/github.com\/docker-library\/repo-info\/blob\/master\/repos\/nextcloud) ([history⁠](https:\/\/github.com\/docker-library\/repo-info\/commits\/master\/repos\/nextcloud))  \n   (image metadata, transfer size, etc)\n- **Image updates**:  \n   [official-images repo's `library\/nextcloud` label⁠](https:\/\/github.com\/docker-library\/official-images\/issues?q=label%3Alibrary%2Fnextcloud)  \n   [official-images repo's `library\/nextcloud` file⁠](https:\/\/github.com\/docker-library\/official-images\/blob\/master\/library\/nextcloud) ([history⁠](https:\/\/github.com\/docker-library\/official-images\/commits\/master\/library\/nextcloud))\n- **Source of this description**:  \n   [docs repo's `nextcloud\/` directory⁠](https:\/\/github.com\/docker-library\/docs\/tree\/master\/nextcloud) ([history⁠](https:\/\/github.com\/docker-library\/docs\/commits\/master\/nextcloud))\n### What is Nextcloud?\nA safe home for all your data. Access & share your files, calendars, contacts, mail & more from any device, on your terms.\n\n> [Nextcloud.com⁠](https:\/\/nextcloud.com\/)\n\nThis Docker micro-service image is developed and maintained by the Nextcloud community. Nextcloud GmbH does not offer support for this Docker image. When you are looking to get professional support, you can become an [enterprise⁠](https:\/\/nextcloud.com\/enterprise\/) customer or use [AIO⁠](https:\/\/github.com\/nextcloud\/all-in-one#nextcloud-all-in-one).\n\n### How to use this image\nThis image is designed to be used in a micro-service environment. There are two versions of the image you can choose from.\n\nThe `apache` tag contains a full Nextcloud installation including an apache web server. It is designed to be easy to use and gets you running pretty fast. This is also the default for the `latest` tag and version tags that are not further specified.\n\nThe second option is a `fpm` container. It is based on the [php-fpm](https:\/\/hub.docker.com\/_\/php\/) image and runs a fastCGI-Process that serves your Nextcloud page. To use this image it must be combined with any webserver that can proxy the http requests to the FastCGI-port of the container.\n\n#### Using the apache image\nThe apache image contains a webserver and exposes port 80. To start the container type:\n\n```\n$ docker run -d -p 8080:80 nextcloud\n```\nCopy\n\nNow you can access Nextcloud at [http:\/\/localhost:8080\/⁠](http:\/\/localhost:8080\/) from your host system.\n\n#### Using the fpm image\nTo use the fpm image, you need an additional web server, such as [nginx⁠](https:\/\/docs.nextcloud.com\/server\/latest\/admin_manual\/installation\/nginx.html), that can proxy http-request to the fpm-port of the container. For fpm connection this container exposes port 9000. In most cases, you might want to use another container or your host as proxy. If you use your host you can address your Nextcloud container directly on port 9000. If you use another container, make sure that you add them to the same docker network (via `docker run --network <NAME> ...` or a `compose.yaml` file). In both cases you don't want to map the fpm port to your host.\n\n```\n$ docker run -d nextcloud:fpm\n```\nCopy\n\nAs the fastCGI-Process is not capable of serving static files (style sheets, images, ...), the webserver needs access to these files. This can be achieved with the `volumes-from` option. You can find more information in the Docker Compose section.\n\n#### Using an external database\nBy default, this container uses SQLite for data storage but the Nextcloud setup wizard (appears on first run) allows connecting to an existing MySQL\/MariaDB or PostgreSQL database. You can also link a database container, e. g. `--link my-mysql:mysql`, and then use `mysql` as the database host on setup. More info is in the Docker Compose section.\n\n#### Persistent data\nThe Nextcloud installation and all data beyond what lives in the database (file uploads, etc.) are stored in the [unnamed docker volume⁠](https:\/\/docs.docker.com\/storage\/volumes\/) volume `\/var\/www\/html`. The docker daemon will store that data within the docker directory `\/var\/lib\/docker\/volumes\/...`. That means your data is saved even if the container crashes, is stopped or deleted.\n\nA named Docker volume or a mounted host directory should be used for upgrades and backups. To achieve this, you need one volume for your database container and one for Nextcloud.\n\nNextcloud:\n\n- `\/var\/www\/html\/` folder where all Nextcloud data lives\n\n```\n$ docker run -d \\\n-v nextcloud:\/var\/www\/html \\\nnextcloud\n```\nCopy\n\nDatabase:\n\n- `\/var\/lib\/mysql` MySQL \/ MariaDB Data\n- `\/var\/lib\/postgresql\/data` PostgreSQL Data\n\n```\n$ docker run -d \\\n-v db:\/var\/lib\/mysql \\\nmariadb:10.6\n```\nCopy\n##### Additional volumes\nIf you want to get fine grained access to your individual files, you can mount additional volumes for data, config, your theme and custom apps. The `data`, `config` files are stored in respective subfolders inside `\/var\/www\/html\/`. The apps are split into core `apps` (which are shipped with Nextcloud and you don't need to take care of) and a `custom_apps` folder. If you use a custom theme it would go into the `themes` subfolder.\n\nOverview of the folders that can be mounted as volumes:\n\n- `\/var\/www\/html` Main folder, needed for updating\n- `\/var\/www\/html\/custom_apps` installed \/ modified apps\n- `\/var\/www\/html\/config` local configuration\n- `\/var\/www\/html\/data` the actual data of your Nextcloud\n- `\/var\/www\/html\/themes\/<YOUR_CUSTOM_THEME>` theming\/branding\n\nIf you want to use named volumes for all of these, it would look like this:\n\n```\n$ docker run -d \\\n-v nextcloud:\/var\/www\/html \\\n-v apps:\/var\/www\/html\/custom_apps \\\n-v config:\/var\/www\/html\/config \\\n-v data:\/var\/www\/html\/data \\\n-v theme:\/var\/www\/html\/themes\/<YOUR_CUSTOM_THEME> \\\nnextcloud\n```\nCopy\n##### Custom volumes\nIf mounting additional volumes under `\/var\/www\/html`, you should consider:\n\n- Confirming that\n  [upgrade.exclude⁠](https:\/\/github.com\/nextcloud\/docker\/blob\/master\/upgrade.exclude)\n  contains the files and folders that should persist during installation and upgrades; or\n- Mounting storage volumes to locations outside of `\/var\/www\/html`.\n\n> You should note that data inside the main folder (`\/var\/www\/html`) will be overridden\/removed during installation and upgrades, unless listed in [upgrade.exclude⁠](https:\/\/github.com\/nextcloud\/docker\/blob\/master\/upgrade.exclude). The additional volumes officially supported are already in that list, but custom volumes will need to be added by you. We suggest mounting custom storage volumes outside of `\/var\/www\/html` and if possible read-only so that making this adjustment is unnecessary. If you must do so, however, you may build a custom image with a modified `\/upgrade.exclude` file that incorporates your custom volume(s).\n#### Using the Nextcloud command-line interface\nTo use the [Nextcloud command-line interface⁠](https:\/\/docs.nextcloud.com\/server\/latest\/admin_manual\/configuration_server\/occ_command.html) (aka. `occ` command):\n\n```\n$ docker exec --user www-data CONTAINER_ID php occ\n```\nCopy\n\nor for `docker compose`:\n\n```\n$ docker compose exec --user www-data app php occ\n```\nCopy\n#### Auto configuration via environment variables\nThe Nextcloud image supports auto configuration via environment variables. You can preconfigure everything that is asked on the install page on first run. To enable auto configuration, set your database connection via the following environment variables. You must specify all of the environment variables for a given database or the database environment variables defaults to SQLITE. ONLY use one database type\\!\n\n**SQLite**:\n\n- `SQLITE_DATABASE` Name of the database using sqlite\n\n**MYSQL\/MariaDB**:\n\n- `MYSQL_DATABASE` Name of the database using mysql \/ mariadb.\n- `MYSQL_USER` Username for the database using mysql \/ mariadb.\n- `MYSQL_PASSWORD` Password for the database user using mysql \/ mariadb.\n- `MYSQL_HOST` Hostname of the database server using mysql \/ mariadb.\n\n**PostgreSQL**:\n\n- `POSTGRES_DB` Name of the database using postgres.\n- `POSTGRES_USER` Username for the database using postgres.\n- `POSTGRES_PASSWORD` Password for the database user using postgres.\n- `POSTGRES_HOST` Hostname of the database server using postgres.\n\nAs an alternative to passing sensitive information via environment variables, `_FILE` may be appended to the previously listed environment variables, causing the initialization script to load the values for those variables from files present in the container. See [Docker secrets](https:\/\/hub.docker.com\/_\/nextcloud\/#docker-secrets) section below.\n\nIf you set any group of values (i.e. all of `MYSQL_DATABASE`, `MYSQL_USER`, `MYSQL_PASSWORD`, `MYSQL_HOST`), they will not be asked in the install page on first run. With a complete configuration by using all variables for your database type, you can additionally configure your Nextcloud instance by setting admin user and password (only works if you set both):\n\n- `NEXTCLOUD_ADMIN_USER` Name of the Nextcloud admin user.\n- `NEXTCLOUD_ADMIN_PASSWORD` Password for the Nextcloud admin user.\n\nIf you want, you can set the data directory, otherwise default value will be used.\n\n- `NEXTCLOUD_DATA_DIR` (default: `\/var\/www\/html\/data`) Configures the data directory where nextcloud stores all files from the users.\n\nOne or more trusted domains can be set through environment variable, too. They will be added to the configuration after install.\n\n- `NEXTCLOUD_TRUSTED_DOMAINS` (not set by default) Optional space-separated list of domains\n\nThe install and update script is only triggered when a default command is used (`apache-foreground` or `php-fpm`). If you use a custom command you have to enable the install \/ update with\n\n- `NEXTCLOUD_UPDATE` (default: `0`)\n\nYou might want to make sure the htaccess is up to date after each container update. Especially on multiple swarm nodes as any discrepancy will make your server unusable.\n\n- `NEXTCLOUD_INIT_HTACCESS` (not set by default) Set it to true to enable run `occ maintenance:update:htaccess` after container initialization.\n\nIf you want to use Redis you have to create a separate [Redis](https:\/\/hub.docker.com\/_\/redis\/) container in your setup \/ in your Compose file. To inform Nextcloud about the Redis container, pass in the following parameters:\n\n- `REDIS_HOST` (not set by default) Name of Redis container\n- `REDIS_HOST_PORT` (default: `6379`) Optional port for Redis, only use for external Redis servers that run on non-standard ports.\n- `REDIS_HOST_PASSWORD` (not set by default) Redis password\n\nThe use of Redis is recommended to prevent file locking problems. See the examples for further instructions.\n\nTo use an external SMTP server, you have to provide the connection details. To configure Nextcloud to use SMTP add:\n\n- `SMTP_HOST` (not set by default): The hostname of the SMTP server.\n- `SMTP_SECURE` (empty by default): Set to `ssl` to use SSL, or `tls` to use STARTTLS.\n- `SMTP_PORT` (default: `465` for SSL and `25` for non-secure connections): Optional port for the SMTP connection. Use `587` for an alternative port for STARTTLS.\n- `SMTP_AUTHTYPE` (default: `LOGIN`): The method used for authentication. Use `PLAIN` if no authentication is required.\n- `SMTP_NAME` (empty by default): The username for the authentication.\n- `SMTP_PASSWORD` (empty by default): The password for the authentication.\n- `MAIL_FROM_ADDRESS` (not set by default): Set the local-part for the 'from' field in the emails sent by Nextcloud.\n- `MAIL_DOMAIN` (not set by default): Set a different domain for the emails than the domain where Nextcloud is installed.\n\nAt least `SMTP_HOST`, `MAIL_FROM_ADDRESS` and `MAIL_DOMAIN` must be set for the configurations to be applied.\n\nCheck the [Nextcloud documentation⁠](https:\/\/docs.nextcloud.com\/server\/latest\/admin_manual\/configuration_server\/email_configuration.html) for other values to configure SMTP.\n\nTo use an external S3 compatible object store as primary storage, set the following variables:\n\n- `OBJECTSTORE_S3_BUCKET`: The name of the bucket that Nextcloud should store the data in\n- `OBJECTSTORE_S3_REGION`: The region that the S3 bucket resides in\n- `OBJECTSTORE_S3_HOST`: The hostname of the object storage server\n- `OBJECTSTORE_S3_PORT`: The port that the object storage server is being served over\n- `OBJECTSTORE_S3_KEY`: AWS style access key\n- `OBJECTSTORE_S3_SECRET`: AWS style secret access key\n- `OBJECTSTORE_S3_STORAGE_CLASS`: The storage class to use when adding objects to the bucket\n- `OBJECTSTORE_S3_SSL` (default: `true`): Whether or not SSL\/TLS should be used to communicate with object storage server\n- `OBJECTSTORE_S3_USEPATH_STYLE` (default: `false`): Not required for AWS S3\n- `OBJECTSTORE_S3_LEGACYAUTH` (default: `false`): Not required for AWS S3\n- `OBJECTSTORE_S3_OBJECT_PREFIX` (default: `urn:oid:`): Prefix to prepend to the fileid\n- `OBJECTSTORE_S3_AUTOCREATE` (default: `true`): Create the container if it does not exist\n- `OBJECTSTORE_S3_SSE_C_KEY` (not set by default): Base64 encoded key with a maximum length of 32 bytes for server side encryption (SSE-C)\n\nCheck the [Nextcloud documentation⁠](https:\/\/docs.nextcloud.com\/server\/latest\/admin_manual\/configuration_files\/primary_storage.html#simple-storage-service-s3) for more information.\n\nTo use an external OpenStack Swift object store as primary storage, set the following variables:\n\n- `OBJECTSTORE_SWIFT_URL`: The Swift identity (Keystone) endpoint\n- `OBJECTSTORE_SWIFT_AUTOCREATE` (default: `false`): Whether or not Nextcloud should automatically create the Swift container\n- `OBJECTSTORE_SWIFT_USER_NAME`: Swift username\n- `OBJECTSTORE_SWIFT_USER_PASSWORD`: Swift user password\n- `OBJECTSTORE_SWIFT_USER_DOMAIN` (default: `Default`): Swift user domain\n- `OBJECTSTORE_SWIFT_PROJECT_NAME`: OpenStack project name\n- `OBJECTSTORE_SWIFT_PROJECT_DOMAIN` (default: `Default`): OpenStack project domain\n- `OBJECTSTORE_SWIFT_SERVICE_NAME` (default: `swift`): Swift service name\n- `OBJECTSTORE_SWIFT_REGION`: Swift endpoint region\n- `OBJECTSTORE_SWIFT_CONTAINER_NAME`: Swift container (bucket) that Nextcloud should store the data in\n\nCheck the [Nextcloud documentation⁠](https:\/\/docs.nextcloud.com\/server\/latest\/admin_manual\/configuration_files\/primary_storage.html#openstack-swift) for more information.\n\nTo customize other PHP limits you can simply change the following variables:\n\n- `PHP_MEMORY_LIMIT` (default `512M`) This sets the maximum amount of memory in bytes that a script is allowed to allocate. This is meant to help prevent poorly written scripts from eating up all available memory but it can prevent normal operation if set too tight.\n- `PHP_UPLOAD_LIMIT` (default `512M`) This sets the upload limit (`post_max_size` and `upload_max_filesize`) for big files. Note that you may have to change other limits depending on your client, webserver or operating system. Check the\n  [Nextcloud documentation⁠](https:\/\/docs.nextcloud.com\/server\/latest\/admin_manual\/configuration_files\/big_file_upload_configuration.html)\n  for more information.\n\nTo customize Apache max file upload limit you can change the following variable:\n\n- `APACHE_BODY_LIMIT` (default `1073741824` \\[1GiB\\]) This restricts the total size of the HTTP request body sent from the client. It specifies the number of *bytes* that are allowed in a request body. A value of **0** means **unlimited**. Check the\n  [Nextcloud documentation⁠](https:\/\/docs.nextcloud.com\/server\/latest\/admin_manual\/configuration_files\/big_file_upload_configuration.html#apache)\n  for more information.\n#### Auto configuration via hook folders\nThere are 5 hooks\n\n- `pre-installation` Executed before the Nextcloud is installed\/initiated\n- `post-installation` Executed after the Nextcloud is installed\/initiated\n- `pre-upgrade` Executed before the Nextcloud is upgraded\n- `post-upgrade` Executed after the Nextcloud is upgraded\n- `before-starting` Executed before the Nextcloud starts\n\nTo use the hooks triggered by the `entrypoint` script, either\n\n- Added your script(s) to the individual of the hook folder(s), which are located at the path `\/docker-entrypoint-hooks.d` in the container\n- Use volume(s) if you want to use script from the host system inside the container, see example.\n\n**Note:** Only the script(s) located in a hook folder (not sub-folders), ending with `.sh` and marked as executable, will be executed.\n\n**Example:** Mount using volumes\n\n```\n...\n  app:\n    image: nextcloud:stable\n\n    volumes:\n      - .\/app-hooks\/pre-installation:\/docker-entrypoint-hooks.d\/pre-installation\n      - .\/app-hooks\/post-installation:\/docker-entrypoint-hooks.d\/post-installation\n      - .\/app-hooks\/pre-upgrade:\/docker-entrypoint-hooks.d\/pre-upgrade\n      - .\/app-hooks\/post-upgrade:\/docker-entrypoint-hooks.d\/post-upgrade\n      - .\/app-hooks\/before-starting:\/docker-entrypoint-hooks.d\/before-starting\n...\n```\nCopy\n#### Using the apache image behind a reverse proxy and auto configure server host and protocol\nThe apache image will replace the remote addr (IP address visible to Nextcloud) with the IP address from `X-Real-IP` if the request is coming from a proxy in `10.0.0.0\/8`, `172.16.0.0\/12` or `192.168.0.0\/16` by default. If you want Nextcloud to pick up the server host (`HTTP_X_FORWARDED_HOST`), protocol (`HTTP_X_FORWARDED_PROTO`) and client IP (`HTTP_X_FORWARDED_FOR`) from a trusted proxy, then disable rewrite IP and add the reverse proxy's IP address to `TRUSTED_PROXIES`.\n\n- `APACHE_DISABLE_REWRITE_IP` (not set by default): Set to 1 to disable rewrite IP.\n- `TRUSTED_PROXIES` (empty by default): A space-separated list of trusted proxies. CIDR notation is supported for IPv4.\n\nIf the `TRUSTED_PROXIES` approach does not work for you, try using fixed values for overwrite parameters.\n\n- `OVERWRITEHOST` (empty by default): Set the hostname of the proxy. Can also specify a port.\n- `OVERWRITEPROTOCOL` (empty by default): Set the protocol of the proxy, http or https.\n- `OVERWRITECLIURL` (empty by default): Set the cli url of the proxy (e.g.\n  [https:\/\/mydnsname.example.com⁠](https:\/\/mydnsname.example.com\/)\n  )\n- `OVERWRITEWEBROOT` (empty by default): Set the absolute path of the proxy.\n- `OVERWRITECONDADDR` (empty by default): Regex to overwrite the values dependent on the remote address.\n\nCheck the [Nexcloud documentation⁠](https:\/\/docs.nextcloud.com\/server\/latest\/admin_manual\/configuration_server\/reverse_proxy_configuration.html) for more details.\n\nKeep in mind that once set, removing these environment variables won't remove these values from the configuration file, due to how Nextcloud merges configuration files together.\n\n### Running this image with Docker Compose\nThe easiest way to get a fully featured and functional setup is using a `compose.yaml` file. There are too many different possibilities to setup your system, so here are only some examples of what you have to look for.\n\nAt first, make sure you have chosen the right base image (fpm or apache) and added features you wanted (see below). In every case, you would want to add a database container and docker volumes to get easy access to your persistent data. When you want to have your server reachable from the internet, adding HTTPS-encryption is mandatory! See below for more information.\n\n#### Base version - apache\nThis version will use the apache image and add a mariaDB container. The volumes are set to keep your data persistent. This setup provides **no ssl encryption** and is intended to run behind a proxy.\n\nMake sure to pass in values for `MYSQL_ROOT_PASSWORD` and `MYSQL_PASSWORD` variables before you run this setup.\n\n```\nvolumes:\n  nextcloud:\n  db:\n\nservices:\n  db:\n    image: mariadb:10.6\n    restart: always\n    command: --transaction-isolation=READ-COMMITTED --log-bin=binlog --binlog-format=ROW\n    volumes:\n      - db:\/var\/lib\/mysql\n    environment:\n      - MYSQL_ROOT_PASSWORD=\n      - MYSQL_PASSWORD=\n      - MYSQL_DATABASE=nextcloud\n      - MYSQL_USER=nextcloud\n\n  app:\n    image: nextcloud\n    restart: always\n    ports:\n      - 8080:80\n    links:\n      - db\n    volumes:\n      - nextcloud:\/var\/www\/html\n    environment:\n      - MYSQL_PASSWORD=\n      - MYSQL_DATABASE=nextcloud\n      - MYSQL_USER=nextcloud\n      - MYSQL_HOST=db\n```\nCopy\n\nThen run `docker compose up -d`, now you can access Nextcloud at [http:\/\/localhost:8080\/⁠](http:\/\/localhost:8080\/) from your host system.\n\n#### Base version - FPM\nWhen using the FPM image, you need another container that acts as web server on port 80 and proxies the requests to the Nextcloud container. In this example a simple nginx container is combined with the Nextcloud-fpm image and a MariaDB database container. The data is stored in docker volumes. The nginx container also needs access to static files from your Nextcloud installation. It gets access to all the volumes mounted to Nextcloud via the `volumes_from` option. The configuration for nginx is stored in the configuration file `nginx.conf`, that is mounted into the container. An example can be found in the examples section [here⁠](https:\/\/github.com\/nextcloud\/docker\/tree\/master\/.examples).\n\nAs this setup does **not include encryption**, it should be run behind a proxy.\n\nMake sure to pass in values for `MYSQL_ROOT_PASSWORD` and `MYSQL_PASSWORD` variables before you run this setup.\n\n```\nvolumes:\n  nextcloud:\n  db:\n\nservices:\n  db:\n    image: mariadb:10.6\n    restart: always\n    command: --transaction-isolation=READ-COMMITTED --log-bin=binlog --binlog-format=ROW\n    volumes:\n      - db:\/var\/lib\/mysql\n    environment:\n      - MYSQL_ROOT_PASSWORD=\n      - MYSQL_PASSWORD=\n      - MYSQL_DATABASE=nextcloud\n      - MYSQL_USER=nextcloud\n\n...\n\n**Note:** the description for this image is longer than the Hub length limit of 25000, so has been trimmed.  The full description can be found at [https:\/\/github.com\/docker-library\/docs\/tree\/master\/nextcloud\/README.md](https:\/\/github.com\/docker-library\/docs\/tree\/master\/nextcloud\/README.md).  See also [docker\/hub-feedback#238](https:\/\/github.com\/docker\/hub-feedback\/issues\/238) and [docker\/roadmap#475](https:\/\/github.com\/docker\/roadmap\/issues\/475).\n```\nCopy\n\n### Tag summary\nRecent tags\n\nstable-fpm-alpine\n\nRecent tags\n\n**Content type**\n\nImage\n\n**Digest**\n\nsha256:dde27986e…\n\n**Size**\n\n361\\.4 MB\n\n**Last updated**\n\n3 days ago\n\n```\ndocker pull nextcloud:stable-fpm-alpine\n```\nCopy\n\n### This week's pulls\nPulls:\n\n580,141\n\nMar 23 to Mar 29\n\n[Learn more⁠](https:\/\/www.docker.com\/partners\/publisher-insights\/)\n\n### About Official Images\nDocker Official Images are a curated set of Docker open source and drop-in solution repositories.\n\n###### Why Official Images?\nThese images have clear documentation, promote best practices, and are designed for the most common use cases.\n\nWhy[Overview](https:\/\/www.docker.com\/why-docker)[What is a Container](https:\/\/www.docker.com\/resources\/what-container)\n\nProducts[Product Overview](https:\/\/www.docker.com\/products)Product Offerings[Docker Desktop](https:\/\/www.docker.com\/products\/docker-desktop)[Docker Hub](https:\/\/www.docker.com\/products\/docker-hub)Features[Container Runtime](https:\/\/www.docker.com\/products\/container-runtime)[Developer Tools](https:\/\/www.docker.com\/products\/developer-tools)[Docker App](https:\/\/www.docker.com\/products\/docker-app)[Kubernetes](https:\/\/www.docker.com\/products\/kubernetes)\n\nDevelopers[Getting Started](https:\/\/docs.docker.com\/get-started)[Play with Docker](https:\/\/www.docker.com\/play-with-docker)[Community](https:\/\/www.docker.com\/docker-community)[Open Source](https:\/\/www.docker.com\/open-source)[Documentation](https:\/\/www.docker.com\/docs)\n\nCompany[About Us](https:\/\/www.docker.com\/company)[Resources](https:\/\/www.docker.com\/resources)[Blog](https:\/\/www.docker.com\/blog\/)[Customers](https:\/\/www.docker.com\/customers)[Partners](https:\/\/www.docker.com\/partners)[Newsroom](https:\/\/www.docker.com\/company\/newsroom)[Events and Webinars](https:\/\/www.docker.com\/events-and-webinars)[Careers](https:\/\/www.docker.com\/careers)[Contact Us](https:\/\/www.docker.com\/company\/contact)\n\n[System Status⁠](https:\/\/www.dockerstatus.com\/)\n***\n© 2026 Docker, Inc. All rights reserved. \\| [Terms of Service](https:\/\/www.docker.com\/legal\/docker-terms-service) \\| [Subscription Service Agreement](https:\/\/www.docker.com\/legal\/docker-subscription-service-agreement) \\| [Privacy](https:\/\/www.docker.com\/legal\/privacy) \\| [Legal](https:\/\/www.docker.com\/legal)\n\nCookies Settings\n\nBack\n\n- System theme\n- Light theme\n- Dark theme\n\nBack\n\n- System theme\n- Light theme\n- Dark theme\n\nBack\n\n[Docker Home Explore and manage your Docker experience.](https:\/\/app.docker.com\/)\n\n[Docker Admin Console Manage users, control access, & set policies.](https:\/\/app.docker.com\/admin)\n\n[Docker Hub Find and share images with your team.](https:\/\/hub.docker.com\/)\n\n[Docker Scout Secure your supply chain at every level.](https:\/\/scout.docker.com\/)\n\n[Docker Desktop Local development, simplified.](https:\/\/hub.docker.com\/open-desktop)\n\n[Docker Build Cloud Speed up your builds.](https:\/\/app.docker.com\/build)\n\n[Testcontainers Cloud New Run integration tests with real dependencies.](https:\/\/app.testcontainers.cloud\/)","attrs_readable_markdown":"**Note:** the description for this image is longer than the Hub length limit of 25000, so has been trimmed. The full description can be found at [https:\/\/github.com\/docker-library\/docs\/tree\/master\/nextcloud\/README.md⁠](https:\/\/github.com\/docker-library\/docs\/tree\/master\/nextcloud\/README.md). See also [docker\/hub-feedback\\#238⁠](https:\/\/github.com\/docker\/hub-feedback\/issues\/238) and [docker\/roadmap\\#475⁠](https:\/\/github.com\/docker\/roadmap\/issues\/475).\n\n### IMPORTANT NOTE\n⚠️⚠️⚠️ This image is maintained by community volunteers and designed for expert use. For quick and easy deployment that supports the full set of Nextcloud Hub features, use the [Nextcloud All-in-One docker container⁠](https:\/\/github.com\/nextcloud\/all-in-one#nextcloud-all-in-one) maintained by Nextcloud GmbH.\n\n### Quick reference\n- **Maintained by**:  \n   [the Nextcloud community⁠](https:\/\/github.com\/nextcloud\/docker)\n- **Where to get help**:  \n   [the Docker Community Slack⁠](https:\/\/dockr.ly\/comm-slack), [Server Fault⁠](https:\/\/serverfault.com\/help\/on-topic), [Unix & Linux⁠](https:\/\/unix.stackexchange.com\/help\/on-topic), or [Stack Overflow⁠](https:\/\/stackoverflow.com\/help\/on-topic)\n### Supported tags and respective `Dockerfile` links\n- [`32.0.8-apache`, `32.0-apache`, `32-apache`, `stable-apache`, `production-apache`, `32.0.8`, `32.0`, `32`, `stable`, `production`⁠](https:\/\/github.com\/nextcloud\/docker\/blob\/efa6ee645631d34047625a82dfddd083324628ef\/32\/apache\/Dockerfile)\n- [`32.0.8-fpm`, `32.0-fpm`, `32-fpm`, `stable-fpm`, `production-fpm`⁠](https:\/\/github.com\/nextcloud\/docker\/blob\/efa6ee645631d34047625a82dfddd083324628ef\/32\/fpm\/Dockerfile)\n- [`32.0.8-fpm-alpine`, `32.0-fpm-alpine`, `32-fpm-alpine`, `stable-fpm-alpine`, `production-fpm-alpine`⁠](https:\/\/github.com\/nextcloud\/docker\/blob\/efa6ee645631d34047625a82dfddd083324628ef\/32\/fpm-alpine\/Dockerfile)\n- [`33.0.2-apache`, `33.0-apache`, `33-apache`, `apache`, `33.0.2`, `33.0`, `33`, `latest`⁠](https:\/\/github.com\/nextcloud\/docker\/blob\/efa6ee645631d34047625a82dfddd083324628ef\/33\/apache\/Dockerfile)\n- [`33.0.2-fpm`, `33.0-fpm`, `33-fpm`, `fpm`⁠](https:\/\/github.com\/nextcloud\/docker\/blob\/efa6ee645631d34047625a82dfddd083324628ef\/33\/fpm\/Dockerfile)\n- [`33.0.2-fpm-alpine`, `33.0-fpm-alpine`, `33-fpm-alpine`, `fpm-alpine`⁠](https:\/\/github.com\/nextcloud\/docker\/blob\/efa6ee645631d34047625a82dfddd083324628ef\/33\/fpm-alpine\/Dockerfile)\n### Quick reference (cont.)\n- **Where to file issues**:  \n   [https:\/\/github.com\/nextcloud\/docker\/issues⁠](https:\/\/github.com\/nextcloud\/docker\/issues?q=)\n- **Supported architectures**: ([more info⁠](https:\/\/github.com\/docker-library\/official-images#architectures-other-than-amd64))  \n   [`amd64`](https:\/\/hub.docker.com\/r\/amd64\/nextcloud\/), [`arm32v5`](https:\/\/hub.docker.com\/r\/arm32v5\/nextcloud\/), [`arm32v6`](https:\/\/hub.docker.com\/r\/arm32v6\/nextcloud\/), [`arm32v7`](https:\/\/hub.docker.com\/r\/arm32v7\/nextcloud\/), [`arm64v8`](https:\/\/hub.docker.com\/r\/arm64v8\/nextcloud\/), [`i386`](https:\/\/hub.docker.com\/r\/i386\/nextcloud\/), [`ppc64le`](https:\/\/hub.docker.com\/r\/ppc64le\/nextcloud\/), [`riscv64`](https:\/\/hub.docker.com\/r\/riscv64\/nextcloud\/), [`s390x`](https:\/\/hub.docker.com\/r\/s390x\/nextcloud\/)\n- **Published image artifact details**:  \n   [repo-info repo's `repos\/nextcloud\/` directory⁠](https:\/\/github.com\/docker-library\/repo-info\/blob\/master\/repos\/nextcloud) ([history⁠](https:\/\/github.com\/docker-library\/repo-info\/commits\/master\/repos\/nextcloud))  \n   (image metadata, transfer size, etc)\n- **Image updates**:  \n   [official-images repo's `library\/nextcloud` label⁠](https:\/\/github.com\/docker-library\/official-images\/issues?q=label%3Alibrary%2Fnextcloud)  \n   [official-images repo's `library\/nextcloud` file⁠](https:\/\/github.com\/docker-library\/official-images\/blob\/master\/library\/nextcloud) ([history⁠](https:\/\/github.com\/docker-library\/official-images\/commits\/master\/library\/nextcloud))\n- **Source of this description**:  \n   [docs repo's `nextcloud\/` directory⁠](https:\/\/github.com\/docker-library\/docs\/tree\/master\/nextcloud) ([history⁠](https:\/\/github.com\/docker-library\/docs\/commits\/master\/nextcloud))\n### What is Nextcloud?\nA safe home for all your data. Access & share your files, calendars, contacts, mail & more from any device, on your terms.\n\nThis Docker micro-service image is developed and maintained by the Nextcloud community. Nextcloud GmbH does not offer support for this Docker image. When you are looking to get professional support, you can become an [enterprise⁠](https:\/\/nextcloud.com\/enterprise\/) customer or use [AIO⁠](https:\/\/github.com\/nextcloud\/all-in-one#nextcloud-all-in-one).\n\n### How to use this image\nThis image is designed to be used in a micro-service environment. There are two versions of the image you can choose from.\n\nThe `apache` tag contains a full Nextcloud installation including an apache web server. It is designed to be easy to use and gets you running pretty fast. This is also the default for the `latest` tag and version tags that are not further specified.\n\nThe second option is a `fpm` container. It is based on the [php-fpm](https:\/\/hub.docker.com\/_\/php\/) image and runs a fastCGI-Process that serves your Nextcloud page. To use this image it must be combined with any webserver that can proxy the http requests to the FastCGI-port of the container.\n\n#### Using the apache image\nThe apache image contains a webserver and exposes port 80. To start the container type:\n```\n$ docker run -d -p 8080:80 nextcloud\n```\nNow you can access Nextcloud at [http:\/\/localhost:8080\/⁠](http:\/\/localhost:8080\/) from your host system.\n\n#### Using the fpm image\nTo use the fpm image, you need an additional web server, such as [nginx⁠](https:\/\/docs.nextcloud.com\/server\/latest\/admin_manual\/installation\/nginx.html), that can proxy http-request to the fpm-port of the container. For fpm connection this container exposes port 9000. In most cases, you might want to use another container or your host as proxy. If you use your host you can address your Nextcloud container directly on port 9000. If you use another container, make sure that you add them to the same docker network (via `docker run --network <NAME> ...` or a `compose.yaml` file). In both cases you don't want to map the fpm port to your host.\n```\n$ docker run -d nextcloud:fpm\n```\nAs the fastCGI-Process is not capable of serving static files (style sheets, images, ...), the webserver needs access to these files. This can be achieved with the `volumes-from` option. You can find more information in the Docker Compose section.\n\n#### Using an external database\nBy default, this container uses SQLite for data storage but the Nextcloud setup wizard (appears on first run) allows connecting to an existing MySQL\/MariaDB or PostgreSQL database. You can also link a database container, e. g. `--link my-mysql:mysql`, and then use `mysql` as the database host on setup. More info is in the Docker Compose section.\n\n#### Persistent data\nThe Nextcloud installation and all data beyond what lives in the database (file uploads, etc.) are stored in the [unnamed docker volume⁠](https:\/\/docs.docker.com\/storage\/volumes\/) volume `\/var\/www\/html`. The docker daemon will store that data within the docker directory `\/var\/lib\/docker\/volumes\/...`. That means your data is saved even if the container crashes, is stopped or deleted.\n\nA named Docker volume or a mounted host directory should be used for upgrades and backups. To achieve this, you need one volume for your database container and one for Nextcloud.\n\nNextcloud:\n\n- `\/var\/www\/html\/` folder where all Nextcloud data lives\n```\n$ docker run -d \\\n-v nextcloud:\/var\/www\/html \\\nnextcloud\n```\nDatabase:\n\n- `\/var\/lib\/mysql` MySQL \/ MariaDB Data\n- `\/var\/lib\/postgresql\/data` PostgreSQL Data\n```\n$ docker run -d \\\n-v db:\/var\/lib\/mysql \\\nmariadb:10.6\n```\n##### Additional volumes\nIf you want to get fine grained access to your individual files, you can mount additional volumes for data, config, your theme and custom apps. The `data`, `config` files are stored in respective subfolders inside `\/var\/www\/html\/`. The apps are split into core `apps` (which are shipped with Nextcloud and you don't need to take care of) and a `custom_apps` folder. If you use a custom theme it would go into the `themes` subfolder.\n\nOverview of the folders that can be mounted as volumes:\n\n- `\/var\/www\/html` Main folder, needed for updating\n- `\/var\/www\/html\/custom_apps` installed \/ modified apps\n- `\/var\/www\/html\/config` local configuration\n- `\/var\/www\/html\/data` the actual data of your Nextcloud\n- `\/var\/www\/html\/themes\/<YOUR_CUSTOM_THEME>` theming\/branding\n\nIf you want to use named volumes for all of these, it would look like this:\n```\n$ docker run -d \\\n-v nextcloud:\/var\/www\/html \\\n-v apps:\/var\/www\/html\/custom_apps \\\n-v config:\/var\/www\/html\/config \\\n-v data:\/var\/www\/html\/data \\\n-v theme:\/var\/www\/html\/themes\/<YOUR_CUSTOM_THEME> \\\nnextcloud\n```\n##### Custom volumes\nIf mounting additional volumes under `\/var\/www\/html`, you should consider:\n\n- Confirming that [upgrade.exclude⁠](https:\/\/github.com\/nextcloud\/docker\/blob\/master\/upgrade.exclude) contains the files and folders that should persist during installation and upgrades; or\n- Mounting storage volumes to locations outside of `\/var\/www\/html`.\n\n> You should note that data inside the main folder (`\/var\/www\/html`) will be overridden\/removed during installation and upgrades, unless listed in [upgrade.exclude⁠](https:\/\/github.com\/nextcloud\/docker\/blob\/master\/upgrade.exclude). The additional volumes officially supported are already in that list, but custom volumes will need to be added by you. We suggest mounting custom storage volumes outside of `\/var\/www\/html` and if possible read-only so that making this adjustment is unnecessary. If you must do so, however, you may build a custom image with a modified `\/upgrade.exclude` file that incorporates your custom volume(s).\n#### Using the Nextcloud command-line interface\nTo use the [Nextcloud command-line interface⁠](https:\/\/docs.nextcloud.com\/server\/latest\/admin_manual\/configuration_server\/occ_command.html) (aka. `occ` command):\n```\n$ docker exec --user www-data CONTAINER_ID php occ\n```\nor for `docker compose`:\n```\n$ docker compose exec --user www-data app php occ\n```\n#### Auto configuration via environment variables\nThe Nextcloud image supports auto configuration via environment variables. You can preconfigure everything that is asked on the install page on first run. To enable auto configuration, set your database connection via the following environment variables. You must specify all of the environment variables for a given database or the database environment variables defaults to SQLITE. ONLY use one database type\\!\n\n**SQLite**:\n\n- `SQLITE_DATABASE` Name of the database using sqlite\n\n**MYSQL\/MariaDB**:\n\n- `MYSQL_DATABASE` Name of the database using mysql \/ mariadb.\n- `MYSQL_USER` Username for the database using mysql \/ mariadb.\n- `MYSQL_PASSWORD` Password for the database user using mysql \/ mariadb.\n- `MYSQL_HOST` Hostname of the database server using mysql \/ mariadb.\n\n**PostgreSQL**:\n\n- `POSTGRES_DB` Name of the database using postgres.\n- `POSTGRES_USER` Username for the database using postgres.\n- `POSTGRES_PASSWORD` Password for the database user using postgres.\n- `POSTGRES_HOST` Hostname of the database server using postgres.\n\nAs an alternative to passing sensitive information via environment variables, `_FILE` may be appended to the previously listed environment variables, causing the initialization script to load the values for those variables from files present in the container. See [Docker secrets](https:\/\/hub.docker.com\/_\/nextcloud\/#docker-secrets) section below.\n\nIf you set any group of values (i.e. all of `MYSQL_DATABASE`, `MYSQL_USER`, `MYSQL_PASSWORD`, `MYSQL_HOST`), they will not be asked in the install page on first run. With a complete configuration by using all variables for your database type, you can additionally configure your Nextcloud instance by setting admin user and password (only works if you set both):\n\n- `NEXTCLOUD_ADMIN_USER` Name of the Nextcloud admin user.\n- `NEXTCLOUD_ADMIN_PASSWORD` Password for the Nextcloud admin user.\n\nIf you want, you can set the data directory, otherwise default value will be used.\n\n- `NEXTCLOUD_DATA_DIR` (default: `\/var\/www\/html\/data`) Configures the data directory where nextcloud stores all files from the users.\n\nOne or more trusted domains can be set through environment variable, too. They will be added to the configuration after install.\n\n- `NEXTCLOUD_TRUSTED_DOMAINS` (not set by default) Optional space-separated list of domains\n\nThe install and update script is only triggered when a default command is used (`apache-foreground` or `php-fpm`). If you use a custom command you have to enable the install \/ update with\n\n- `NEXTCLOUD_UPDATE` (default: `0`)\n\nYou might want to make sure the htaccess is up to date after each container update. Especially on multiple swarm nodes as any discrepancy will make your server unusable.\n\n- `NEXTCLOUD_INIT_HTACCESS` (not set by default) Set it to true to enable run `occ maintenance:update:htaccess` after container initialization.\n\nIf you want to use Redis you have to create a separate [Redis](https:\/\/hub.docker.com\/_\/redis\/) container in your setup \/ in your Compose file. To inform Nextcloud about the Redis container, pass in the following parameters:\n\n- `REDIS_HOST` (not set by default) Name of Redis container\n- `REDIS_HOST_PORT` (default: `6379`) Optional port for Redis, only use for external Redis servers that run on non-standard ports.\n- `REDIS_HOST_PASSWORD` (not set by default) Redis password\n\nThe use of Redis is recommended to prevent file locking problems. See the examples for further instructions.\n\nTo use an external SMTP server, you have to provide the connection details. To configure Nextcloud to use SMTP add:\n\n- `SMTP_HOST` (not set by default): The hostname of the SMTP server.\n- `SMTP_SECURE` (empty by default): Set to `ssl` to use SSL, or `tls` to use STARTTLS.\n- `SMTP_PORT` (default: `465` for SSL and `25` for non-secure connections): Optional port for the SMTP connection. Use `587` for an alternative port for STARTTLS.\n- `SMTP_AUTHTYPE` (default: `LOGIN`): The method used for authentication. Use `PLAIN` if no authentication is required.\n- `SMTP_NAME` (empty by default): The username for the authentication.\n- `SMTP_PASSWORD` (empty by default): The password for the authentication.\n- `MAIL_FROM_ADDRESS` (not set by default): Set the local-part for the 'from' field in the emails sent by Nextcloud.\n- `MAIL_DOMAIN` (not set by default): Set a different domain for the emails than the domain where Nextcloud is installed.\n\nAt least `SMTP_HOST`, `MAIL_FROM_ADDRESS` and `MAIL_DOMAIN` must be set for the configurations to be applied.\n\nCheck the [Nextcloud documentation⁠](https:\/\/docs.nextcloud.com\/server\/latest\/admin_manual\/configuration_server\/email_configuration.html) for other values to configure SMTP.\n\nTo use an external S3 compatible object store as primary storage, set the following variables:\n\n- `OBJECTSTORE_S3_BUCKET`: The name of the bucket that Nextcloud should store the data in\n- `OBJECTSTORE_S3_REGION`: The region that the S3 bucket resides in\n- `OBJECTSTORE_S3_HOST`: The hostname of the object storage server\n- `OBJECTSTORE_S3_PORT`: The port that the object storage server is being served over\n- `OBJECTSTORE_S3_KEY`: AWS style access key\n- `OBJECTSTORE_S3_SECRET`: AWS style secret access key\n- `OBJECTSTORE_S3_STORAGE_CLASS`: The storage class to use when adding objects to the bucket\n- `OBJECTSTORE_S3_SSL` (default: `true`): Whether or not SSL\/TLS should be used to communicate with object storage server\n- `OBJECTSTORE_S3_USEPATH_STYLE` (default: `false`): Not required for AWS S3\n- `OBJECTSTORE_S3_LEGACYAUTH` (default: `false`): Not required for AWS S3\n- `OBJECTSTORE_S3_OBJECT_PREFIX` (default: `urn:oid:`): Prefix to prepend to the fileid\n- `OBJECTSTORE_S3_AUTOCREATE` (default: `true`): Create the container if it does not exist\n- `OBJECTSTORE_S3_SSE_C_KEY` (not set by default): Base64 encoded key with a maximum length of 32 bytes for server side encryption (SSE-C)\n\nCheck the [Nextcloud documentation⁠](https:\/\/docs.nextcloud.com\/server\/latest\/admin_manual\/configuration_files\/primary_storage.html#simple-storage-service-s3) for more information.\n\nTo use an external OpenStack Swift object store as primary storage, set the following variables:\n\n- `OBJECTSTORE_SWIFT_URL`: The Swift identity (Keystone) endpoint\n- `OBJECTSTORE_SWIFT_AUTOCREATE` (default: `false`): Whether or not Nextcloud should automatically create the Swift container\n- `OBJECTSTORE_SWIFT_USER_NAME`: Swift username\n- `OBJECTSTORE_SWIFT_USER_PASSWORD`: Swift user password\n- `OBJECTSTORE_SWIFT_USER_DOMAIN` (default: `Default`): Swift user domain\n- `OBJECTSTORE_SWIFT_PROJECT_NAME`: OpenStack project name\n- `OBJECTSTORE_SWIFT_PROJECT_DOMAIN` (default: `Default`): OpenStack project domain\n- `OBJECTSTORE_SWIFT_SERVICE_NAME` (default: `swift`): Swift service name\n- `OBJECTSTORE_SWIFT_REGION`: Swift endpoint region\n- `OBJECTSTORE_SWIFT_CONTAINER_NAME`: Swift container (bucket) that Nextcloud should store the data in\n\nCheck the [Nextcloud documentation⁠](https:\/\/docs.nextcloud.com\/server\/latest\/admin_manual\/configuration_files\/primary_storage.html#openstack-swift) for more information.\n\nTo customize other PHP limits you can simply change the following variables:\n\n- `PHP_MEMORY_LIMIT` (default `512M`) This sets the maximum amount of memory in bytes that a script is allowed to allocate. This is meant to help prevent poorly written scripts from eating up all available memory but it can prevent normal operation if set too tight.\n- `PHP_UPLOAD_LIMIT` (default `512M`) This sets the upload limit (`post_max_size` and `upload_max_filesize`) for big files. Note that you may have to change other limits depending on your client, webserver or operating system. Check the [Nextcloud documentation⁠](https:\/\/docs.nextcloud.com\/server\/latest\/admin_manual\/configuration_files\/big_file_upload_configuration.html) for more information.\n\nTo customize Apache max file upload limit you can change the following variable:\n\n- `APACHE_BODY_LIMIT` (default `1073741824` \\[1GiB\\]) This restricts the total size of the HTTP request body sent from the client. It specifies the number of *bytes* that are allowed in a request body. A value of **0** means **unlimited**. Check the [Nextcloud documentation⁠](https:\/\/docs.nextcloud.com\/server\/latest\/admin_manual\/configuration_files\/big_file_upload_configuration.html#apache) for more information.\n#### Auto configuration via hook folders\nThere are 5 hooks\n\n- `pre-installation` Executed before the Nextcloud is installed\/initiated\n- `post-installation` Executed after the Nextcloud is installed\/initiated\n- `pre-upgrade` Executed before the Nextcloud is upgraded\n- `post-upgrade` Executed after the Nextcloud is upgraded\n- `before-starting` Executed before the Nextcloud starts\n\nTo use the hooks triggered by the `entrypoint` script, either\n\n- Added your script(s) to the individual of the hook folder(s), which are located at the path `\/docker-entrypoint-hooks.d` in the container\n- Use volume(s) if you want to use script from the host system inside the container, see example.\n\n**Note:** Only the script(s) located in a hook folder (not sub-folders), ending with `.sh` and marked as executable, will be executed.\n\n**Example:** Mount using volumes\n```\n...\n  app:\n    image: nextcloud:stable\n\n    volumes:\n      - .\/app-hooks\/pre-installation:\/docker-entrypoint-hooks.d\/pre-installation\n      - .\/app-hooks\/post-installation:\/docker-entrypoint-hooks.d\/post-installation\n      - .\/app-hooks\/pre-upgrade:\/docker-entrypoint-hooks.d\/pre-upgrade\n      - .\/app-hooks\/post-upgrade:\/docker-entrypoint-hooks.d\/post-upgrade\n      - .\/app-hooks\/before-starting:\/docker-entrypoint-hooks.d\/before-starting\n...\n```\n#### Using the apache image behind a reverse proxy and auto configure server host and protocol\nThe apache image will replace the remote addr (IP address visible to Nextcloud) with the IP address from `X-Real-IP` if the request is coming from a proxy in `10.0.0.0\/8`, `172.16.0.0\/12` or `192.168.0.0\/16` by default. If you want Nextcloud to pick up the server host (`HTTP_X_FORWARDED_HOST`), protocol (`HTTP_X_FORWARDED_PROTO`) and client IP (`HTTP_X_FORWARDED_FOR`) from a trusted proxy, then disable rewrite IP and add the reverse proxy's IP address to `TRUSTED_PROXIES`.\n\n- `APACHE_DISABLE_REWRITE_IP` (not set by default): Set to 1 to disable rewrite IP.\n- `TRUSTED_PROXIES` (empty by default): A space-separated list of trusted proxies. CIDR notation is supported for IPv4.\n\nIf the `TRUSTED_PROXIES` approach does not work for you, try using fixed values for overwrite parameters.\n\n- `OVERWRITEHOST` (empty by default): Set the hostname of the proxy. Can also specify a port.\n- `OVERWRITEPROTOCOL` (empty by default): Set the protocol of the proxy, http or https.\n- `OVERWRITECLIURL` (empty by default): Set the cli url of the proxy (e.g. [https:\/\/mydnsname.example.com⁠](https:\/\/mydnsname.example.com\/))\n- `OVERWRITEWEBROOT` (empty by default): Set the absolute path of the proxy.\n- `OVERWRITECONDADDR` (empty by default): Regex to overwrite the values dependent on the remote address.\n\nCheck the [Nexcloud documentation⁠](https:\/\/docs.nextcloud.com\/server\/latest\/admin_manual\/configuration_server\/reverse_proxy_configuration.html) for more details.\n\nKeep in mind that once set, removing these environment variables won't remove these values from the configuration file, due to how Nextcloud merges configuration files together.\n\n### Running this image with Docker Compose\nThe easiest way to get a fully featured and functional setup is using a `compose.yaml` file. There are too many different possibilities to setup your system, so here are only some examples of what you have to look for.\n\nAt first, make sure you have chosen the right base image (fpm or apache) and added features you wanted (see below). In every case, you would want to add a database container and docker volumes to get easy access to your persistent data. When you want to have your server reachable from the internet, adding HTTPS-encryption is mandatory! See below for more information.\n\n#### Base version - apache\nThis version will use the apache image and add a mariaDB container. The volumes are set to keep your data persistent. This setup provides **no ssl encryption** and is intended to run behind a proxy.\n\nMake sure to pass in values for `MYSQL_ROOT_PASSWORD` and `MYSQL_PASSWORD` variables before you run this setup.\n```\nvolumes:\n  nextcloud:\n  db:\n\nservices:\n  db:\n    image: mariadb:10.6\n    restart: always\n    command: --transaction-isolation=READ-COMMITTED --log-bin=binlog --binlog-format=ROW\n    volumes:\n      - db:\/var\/lib\/mysql\n    environment:\n      - MYSQL_ROOT_PASSWORD=\n      - MYSQL_PASSWORD=\n      - MYSQL_DATABASE=nextcloud\n      - MYSQL_USER=nextcloud\n\n  app:\n    image: nextcloud\n    restart: always\n    ports:\n      - 8080:80\n    links:\n      - db\n    volumes:\n      - nextcloud:\/var\/www\/html\n    environment:\n      - MYSQL_PASSWORD=\n      - MYSQL_DATABASE=nextcloud\n      - MYSQL_USER=nextcloud\n      - MYSQL_HOST=db\n```\nThen run `docker compose up -d`, now you can access Nextcloud at [http:\/\/localhost:8080\/⁠](http:\/\/localhost:8080\/) from your host system.\n\n#### Base version - FPM\nWhen using the FPM image, you need another container that acts as web server on port 80 and proxies the requests to the Nextcloud container. In this example a simple nginx container is combined with the Nextcloud-fpm image and a MariaDB database container. The data is stored in docker volumes. The nginx container also needs access to static files from your Nextcloud installation. It gets access to all the volumes mounted to Nextcloud via the `volumes_from` option. The configuration for nginx is stored in the configuration file `nginx.conf`, that is mounted into the container. An example can be found in the examples section [here⁠](https:\/\/github.com\/nextcloud\/docker\/tree\/master\/.examples).\n\nAs this setup does **not include encryption**, it should be run behind a proxy.\n\nMake sure to pass in values for `MYSQL_ROOT_PASSWORD` and `MYSQL_PASSWORD` variables before you run this setup.\n```\nvolumes:\n  nextcloud:\n  db:\n\nservices:\n  db:\n    image: mariadb:10.6\n    restart: always\n    command: --transaction-isolation=READ-COMMITTED --log-bin=binlog --binlog-format=ROW\n    volumes:\n      - db:\/var\/lib\/mysql\n    environment:\n      - MYSQL_ROOT_PASSWORD=\n      - MYSQL_PASSWORD=\n      - MYSQL_DATABASE=nextcloud\n      - MYSQL_USER=nextcloud\n\n...\n\n**Note:** the description for this image is longer than the Hub length limit of 25000, so has been trimmed.  The full description can be found at [https:\/\/github.com\/docker-library\/docs\/tree\/master\/nextcloud\/README.md](https:\/\/github.com\/docker-library\/docs\/tree\/master\/nextcloud\/README.md).  See also [docker\/hub-feedback#238](https:\/\/github.com\/docker\/hub-feedback\/issues\/238) and [docker\/roadmap#475](https:\/\/github.com\/docker\/roadmap\/issues\/475).\n```","meta_canonical":null}

3. Robots.txt Check

Query:

Response:

4. Spam/Ban Check

Query:

Response:

5. Seen Status Check

ℹ️ Skipped - page is already crawled

📄

INDEXABLE

✅

CRAWLED

17 hours ago

🤖

ROBOTS ALLOWED

Page Info Filters

Filter	Status	Condition	Details
HTTP status	PASS	`download_http_code = 200`	HTTP 200
Age cutoff	PASS	`download_stamp > now() - 6 MONTH`	0 months ago
History drop	PASS	`isNull(history_drop_reason)`	No drop reason
Spam/ban	PASS	`fh_dont_index != 1 AND ml_spam_score = 0`	ml_spam_score=0
Canonical	PASS	`meta_canonical IS NULL OR = '' OR = src_unparsed`	Not set

Page Details

Property	Value
URL	https://hub.docker.com/_/nextcloud/
Last Crawled	2026-04-06 10:21:40 (17 hours ago)
First Indexed	2017-01-05 03:47:03 (9 years ago)
HTTP Status Code	200
Meta Title	nextcloud - Official Image \| Docker Hub
Meta Description	Nextcloud manual docker image
Meta Canonical	null
Boilerpipe Text	Note: the description for this image is longer than the Hub length limit of 25000, so has been trimmed. The full description can be found at https://github.com/docker-library/docs/tree/master/nextcloud/README.md ⁠ . See also docker/hub-feedback#238 ⁠ and docker/roadmap#475 ⁠ . IMPORTANT NOTE ⚠️⚠️⚠️ This image is maintained by community volunteers and designed for expert use. For quick and easy deployment that supports the full set of Nextcloud Hub features, use the Nextcloud All-in-One docker container ⁠ maintained by Nextcloud GmbH. Quick reference Maintained by : the Nextcloud community ⁠ Where to get help : the Docker Community Slack ⁠ , Server Fault ⁠ , Unix & Linux ⁠ , or Stack Overflow ⁠ Supported tags and respective Dockerfile links 32.0.8-apache , 32.0-apache , 32-apache , stable-apache , production-apache , 32.0.8 , 32.0 , 32 , stable , production ⁠ 32.0.8-fpm , 32.0-fpm , 32-fpm , stable-fpm , production-fpm ⁠ 32.0.8-fpm-alpine , 32.0-fpm-alpine , 32-fpm-alpine , stable-fpm-alpine , production-fpm-alpine ⁠ 33.0.2-apache , 33.0-apache , 33-apache , apache , 33.0.2 , 33.0 , 33 , latest ⁠ 33.0.2-fpm , 33.0-fpm , 33-fpm , fpm ⁠ 33.0.2-fpm-alpine , 33.0-fpm-alpine , 33-fpm-alpine , fpm-alpine ⁠ Quick reference (cont.) Where to file issues : https://github.com/nextcloud/docker/issues ⁠ Supported architectures : ( more info ⁠ ) amd64 , arm32v5 , arm32v6 , arm32v7 , arm64v8 , i386 , ppc64le , riscv64 , s390x Published image artifact details : repo-info repo's repos/nextcloud/ directory ⁠ ( history ⁠ ) (image metadata, transfer size, etc) Image updates : official-images repo's library/nextcloud label ⁠ official-images repo's library/nextcloud file ⁠ ( history ⁠ ) Source of this description : docs repo's nextcloud/ directory ⁠ ( history ⁠ ) What is Nextcloud? A safe home for all your data. Access & share your files, calendars, contacts, mail & more from any device, on your terms. This Docker micro-service image is developed and maintained by the Nextcloud community. Nextcloud GmbH does not offer support for this Docker image. When you are looking to get professional support, you can become an enterprise ⁠ customer or use AIO ⁠ . How to use this image This image is designed to be used in a micro-service environment. There are two versions of the image you can choose from. The apache tag contains a full Nextcloud installation including an apache web server. It is designed to be easy to use and gets you running pretty fast. This is also the default for the latest tag and version tags that are not further specified. The second option is a fpm container. It is based on the php-fpm image and runs a fastCGI-Process that serves your Nextcloud page. To use this image it must be combined with any webserver that can proxy the http requests to the FastCGI-port of the container. Using the apache image The apache image contains a webserver and exposes port 80. To start the container type: $ docker run -d -p 8080:80 nextcloud Now you can access Nextcloud at http://localhost:8080/ ⁠ from your host system. Using the fpm image To use the fpm image, you need an additional web server, such as nginx ⁠ , that can proxy http-request to the fpm-port of the container. For fpm connection this container exposes port 9000. In most cases, you might want to use another container or your host as proxy. If you use your host you can address your Nextcloud container directly on port 9000. If you use another container, make sure that you add them to the same docker network (via docker run --network <NAME> ... or a compose.yaml file). In both cases you don't want to map the fpm port to your host. $ docker run -d nextcloud:fpm As the fastCGI-Process is not capable of serving static files (style sheets, images, ...), the webserver needs access to these files. This can be achieved with the volumes-from option. You can find more information in the Docker Compose section. Using an external database By default, this container uses SQLite for data storage but the Nextcloud setup wizard (appears on first run) allows connecting to an existing MySQL/MariaDB or PostgreSQL database. You can also link a database container, e. g. --link my-mysql:mysql , and then use mysql as the database host on setup. More info is in the Docker Compose section. Persistent data The Nextcloud installation and all data beyond what lives in the database (file uploads, etc.) are stored in the unnamed docker volume ⁠ volume /var/www/html . The docker daemon will store that data within the docker directory /var/lib/docker/volumes/... . That means your data is saved even if the container crashes, is stopped or deleted. A named Docker volume or a mounted host directory should be used for upgrades and backups. To achieve this, you need one volume for your database container and one for Nextcloud. Nextcloud: /var/www/html/ folder where all Nextcloud data lives $ docker run -d \ -v nextcloud:/var/www/html \ nextcloud Database: /var/lib/mysql MySQL / MariaDB Data /var/lib/postgresql/data PostgreSQL Data $ docker run -d \ -v db:/var/lib/mysql \ mariadb:10.6 Additional volumes If you want to get fine grained access to your individual files, you can mount additional volumes for data, config, your theme and custom apps. The data , config files are stored in respective subfolders inside /var/www/html/ . The apps are split into core apps (which are shipped with Nextcloud and you don't need to take care of) and a custom_apps folder. If you use a custom theme it would go into the themes subfolder. Overview of the folders that can be mounted as volumes: /var/www/html Main folder, needed for updating /var/www/html/custom_apps installed / modified apps /var/www/html/config local configuration /var/www/html/data the actual data of your Nextcloud /var/www/html/themes/<YOUR_CUSTOM_THEME> theming/branding If you want to use named volumes for all of these, it would look like this: $ docker run -d \ -v nextcloud:/var/www/html \ -v apps:/var/www/html/custom_apps \ -v config:/var/www/html/config \ -v data:/var/www/html/data \ -v theme:/var/www/html/themes/<YOUR_CUSTOM_THEME> \ nextcloud Custom volumes If mounting additional volumes under /var/www/html , you should consider: Confirming that upgrade.exclude ⁠ contains the files and folders that should persist during installation and upgrades; or Mounting storage volumes to locations outside of /var/www/html . You should note that data inside the main folder ( /var/www/html ) will be overridden/removed during installation and upgrades, unless listed in upgrade.exclude ⁠ . The additional volumes officially supported are already in that list, but custom volumes will need to be added by you. We suggest mounting custom storage volumes outside of /var/www/html and if possible read-only so that making this adjustment is unnecessary. If you must do so, however, you may build a custom image with a modified /upgrade.exclude file that incorporates your custom volume(s). Using the Nextcloud command-line interface To use the Nextcloud command-line interface ⁠ (aka. occ command): $ docker exec --user www-data CONTAINER_ID php occ or for docker compose : $ docker compose exec --user www-data app php occ Auto configuration via environment variables The Nextcloud image supports auto configuration via environment variables. You can preconfigure everything that is asked on the install page on first run. To enable auto configuration, set your database connection via the following environment variables. You must specify all of the environment variables for a given database or the database environment variables defaults to SQLITE. ONLY use one database type! SQLite : SQLITE_DATABASE Name of the database using sqlite MYSQL/MariaDB : MYSQL_DATABASE Name of the database using mysql / mariadb. MYSQL_USER Username for the database using mysql / mariadb. MYSQL_PASSWORD Password for the database user using mysql / mariadb. MYSQL_HOST Hostname of the database server using mysql / mariadb. PostgreSQL : POSTGRES_DB Name of the database using postgres. POSTGRES_USER Username for the database using postgres. POSTGRES_PASSWORD Password for the database user using postgres. POSTGRES_HOST Hostname of the database server using postgres. As an alternative to passing sensitive information via environment variables, _FILE may be appended to the previously listed environment variables, causing the initialization script to load the values for those variables from files present in the container. See Docker secrets section below. If you set any group of values (i.e. all of MYSQL_DATABASE , MYSQL_USER , MYSQL_PASSWORD , MYSQL_HOST ), they will not be asked in the install page on first run. With a complete configuration by using all variables for your database type, you can additionally configure your Nextcloud instance by setting admin user and password (only works if you set both): NEXTCLOUD_ADMIN_USER Name of the Nextcloud admin user. NEXTCLOUD_ADMIN_PASSWORD Password for the Nextcloud admin user. If you want, you can set the data directory, otherwise default value will be used. NEXTCLOUD_DATA_DIR (default: /var/www/html/data ) Configures the data directory where nextcloud stores all files from the users. One or more trusted domains can be set through environment variable, too. They will be added to the configuration after install. NEXTCLOUD_TRUSTED_DOMAINS (not set by default) Optional space-separated list of domains The install and update script is only triggered when a default command is used ( apache-foreground or php-fpm ). If you use a custom command you have to enable the install / update with NEXTCLOUD_UPDATE (default: 0 ) You might want to make sure the htaccess is up to date after each container update. Especially on multiple swarm nodes as any discrepancy will make your server unusable. NEXTCLOUD_INIT_HTACCESS (not set by default) Set it to true to enable run occ maintenance:update:htaccess after container initialization. If you want to use Redis you have to create a separate Redis container in your setup / in your Compose file. To inform Nextcloud about the Redis container, pass in the following parameters: REDIS_HOST (not set by default) Name of Redis container REDIS_HOST_PORT (default: 6379 ) Optional port for Redis, only use for external Redis servers that run on non-standard ports. REDIS_HOST_PASSWORD (not set by default) Redis password The use of Redis is recommended to prevent file locking problems. See the examples for further instructions. To use an external SMTP server, you have to provide the connection details. To configure Nextcloud to use SMTP add: SMTP_HOST (not set by default): The hostname of the SMTP server. SMTP_SECURE (empty by default): Set to ssl to use SSL, or tls to use STARTTLS. SMTP_PORT (default: 465 for SSL and 25 for non-secure connections): Optional port for the SMTP connection. Use 587 for an alternative port for STARTTLS. SMTP_AUTHTYPE (default: LOGIN ): The method used for authentication. Use PLAIN if no authentication is required. SMTP_NAME (empty by default): The username for the authentication. SMTP_PASSWORD (empty by default): The password for the authentication. MAIL_FROM_ADDRESS (not set by default): Set the local-part for the 'from' field in the emails sent by Nextcloud. MAIL_DOMAIN (not set by default): Set a different domain for the emails than the domain where Nextcloud is installed. At least SMTP_HOST , MAIL_FROM_ADDRESS and MAIL_DOMAIN must be set for the configurations to be applied. Check the Nextcloud documentation ⁠ for other values to configure SMTP. To use an external S3 compatible object store as primary storage, set the following variables: OBJECTSTORE_S3_BUCKET : The name of the bucket that Nextcloud should store the data in OBJECTSTORE_S3_REGION : The region that the S3 bucket resides in OBJECTSTORE_S3_HOST : The hostname of the object storage server OBJECTSTORE_S3_PORT : The port that the object storage server is being served over OBJECTSTORE_S3_KEY : AWS style access key OBJECTSTORE_S3_SECRET : AWS style secret access key OBJECTSTORE_S3_STORAGE_CLASS : The storage class to use when adding objects to the bucket OBJECTSTORE_S3_SSL (default: true ): Whether or not SSL/TLS should be used to communicate with object storage server OBJECTSTORE_S3_USEPATH_STYLE (default: false ): Not required for AWS S3 OBJECTSTORE_S3_LEGACYAUTH (default: false ): Not required for AWS S3 OBJECTSTORE_S3_OBJECT_PREFIX (default: urn:oid: ): Prefix to prepend to the fileid OBJECTSTORE_S3_AUTOCREATE (default: true ): Create the container if it does not exist OBJECTSTORE_S3_SSE_C_KEY (not set by default): Base64 encoded key with a maximum length of 32 bytes for server side encryption (SSE-C) Check the Nextcloud documentation ⁠ for more information. To use an external OpenStack Swift object store as primary storage, set the following variables: OBJECTSTORE_SWIFT_URL : The Swift identity (Keystone) endpoint OBJECTSTORE_SWIFT_AUTOCREATE (default: false ): Whether or not Nextcloud should automatically create the Swift container OBJECTSTORE_SWIFT_USER_NAME : Swift username OBJECTSTORE_SWIFT_USER_PASSWORD : Swift user password OBJECTSTORE_SWIFT_USER_DOMAIN (default: Default ): Swift user domain OBJECTSTORE_SWIFT_PROJECT_NAME : OpenStack project name OBJECTSTORE_SWIFT_PROJECT_DOMAIN (default: Default ): OpenStack project domain OBJECTSTORE_SWIFT_SERVICE_NAME (default: swift ): Swift service name OBJECTSTORE_SWIFT_REGION : Swift endpoint region OBJECTSTORE_SWIFT_CONTAINER_NAME : Swift container (bucket) that Nextcloud should store the data in Check the Nextcloud documentation ⁠ for more information. To customize other PHP limits you can simply change the following variables: PHP_MEMORY_LIMIT (default 512M ) This sets the maximum amount of memory in bytes that a script is allowed to allocate. This is meant to help prevent poorly written scripts from eating up all available memory but it can prevent normal operation if set too tight. PHP_UPLOAD_LIMIT (default 512M ) This sets the upload limit ( post_max_size and upload_max_filesize ) for big files. Note that you may have to change other limits depending on your client, webserver or operating system. Check the Nextcloud documentation ⁠ for more information. To customize Apache max file upload limit you can change the following variable: APACHE_BODY_LIMIT (default 1073741824 [1GiB]) This restricts the total size of the HTTP request body sent from the client. It specifies the number of bytes that are allowed in a request body. A value of 0 means unlimited . Check the Nextcloud documentation ⁠ for more information. Auto configuration via hook folders There are 5 hooks pre-installation Executed before the Nextcloud is installed/initiated post-installation Executed after the Nextcloud is installed/initiated pre-upgrade Executed before the Nextcloud is upgraded post-upgrade Executed after the Nextcloud is upgraded before-starting Executed before the Nextcloud starts To use the hooks triggered by the entrypoint script, either Added your script(s) to the individual of the hook folder(s), which are located at the path /docker-entrypoint-hooks.d in the container Use volume(s) if you want to use script from the host system inside the container, see example. Note: Only the script(s) located in a hook folder (not sub-folders), ending with .sh and marked as executable, will be executed. Example: Mount using volumes ... app: image: nextcloud:stable volumes: - ./app-hooks/pre-installation:/docker-entrypoint-hooks.d/pre-installation - ./app-hooks/post-installation:/docker-entrypoint-hooks.d/post-installation - ./app-hooks/pre-upgrade:/docker-entrypoint-hooks.d/pre-upgrade - ./app-hooks/post-upgrade:/docker-entrypoint-hooks.d/post-upgrade - ./app-hooks/before-starting:/docker-entrypoint-hooks.d/before-starting ... Using the apache image behind a reverse proxy and auto configure server host and protocol The apache image will replace the remote addr (IP address visible to Nextcloud) with the IP address from X-Real-IP if the request is coming from a proxy in 10.0.0.0/8 , 172.16.0.0/12 or 192.168.0.0/16 by default. If you want Nextcloud to pick up the server host ( HTTP_X_FORWARDED_HOST ), protocol ( HTTP_X_FORWARDED_PROTO ) and client IP ( HTTP_X_FORWARDED_FOR ) from a trusted proxy, then disable rewrite IP and add the reverse proxy's IP address to TRUSTED_PROXIES . APACHE_DISABLE_REWRITE_IP (not set by default): Set to 1 to disable rewrite IP. TRUSTED_PROXIES (empty by default): A space-separated list of trusted proxies. CIDR notation is supported for IPv4. If the TRUSTED_PROXIES approach does not work for you, try using fixed values for overwrite parameters. OVERWRITEHOST (empty by default): Set the hostname of the proxy. Can also specify a port. OVERWRITEPROTOCOL (empty by default): Set the protocol of the proxy, http or https. OVERWRITECLIURL (empty by default): Set the cli url of the proxy (e.g. https://mydnsname.example.com ⁠ ) OVERWRITEWEBROOT (empty by default): Set the absolute path of the proxy. OVERWRITECONDADDR (empty by default): Regex to overwrite the values dependent on the remote address. Check the Nexcloud documentation ⁠ for more details. Keep in mind that once set, removing these environment variables won't remove these values from the configuration file, due to how Nextcloud merges configuration files together. Running this image with Docker Compose The easiest way to get a fully featured and functional setup is using a compose.yaml file. There are too many different possibilities to setup your system, so here are only some examples of what you have to look for. At first, make sure you have chosen the right base image (fpm or apache) and added features you wanted (see below). In every case, you would want to add a database container and docker volumes to get easy access to your persistent data. When you want to have your server reachable from the internet, adding HTTPS-encryption is mandatory! See below for more information. Base version - apache This version will use the apache image and add a mariaDB container. The volumes are set to keep your data persistent. This setup provides no ssl encryption and is intended to run behind a proxy. Make sure to pass in values for MYSQL_ROOT_PASSWORD and MYSQL_PASSWORD variables before you run this setup. volumes: nextcloud: db: services: db: image: mariadb:10.6 restart: always command: --transaction-isolation=READ-COMMITTED --log-bin=binlog --binlog-format=ROW volumes: - db:/var/lib/mysql environment: - MYSQL_ROOT_PASSWORD= - MYSQL_PASSWORD= - MYSQL_DATABASE=nextcloud - MYSQL_USER=nextcloud app: image: nextcloud restart: always ports: - 8080 :80 links: - db volumes: - nextcloud:/var/www/html environment: - MYSQL_PASSWORD= - MYSQL_DATABASE=nextcloud - MYSQL_USER=nextcloud - MYSQL_HOST=db Then run docker compose up -d , now you can access Nextcloud at http://localhost:8080/ ⁠ from your host system. Base version - FPM When using the FPM image, you need another container that acts as web server on port 80 and proxies the requests to the Nextcloud container. In this example a simple nginx container is combined with the Nextcloud-fpm image and a MariaDB database container. The data is stored in docker volumes. The nginx container also needs access to static files from your Nextcloud installation. It gets access to all the volumes mounted to Nextcloud via the volumes_from option. The configuration for nginx is stored in the configuration file nginx.conf , that is mounted into the container. An example can be found in the examples section here ⁠ . As this setup does not include encryption , it should be run behind a proxy. Make sure to pass in values for MYSQL_ROOT_PASSWORD and MYSQL_PASSWORD variables before you run this setup. volumes: nextcloud: db: services: db: image: mariadb:10.6 restart: always command: --transaction-isolation=READ-COMMITTED --log-bin=binlog --binlog-format=ROW volumes: - db:/var/lib/mysql environment: - MYSQL_ROOT_PASSWORD= - MYSQL_PASSWORD= - MYSQL_DATABASE=nextcloud - MYSQL_USER=nextcloud ... Note: the description for this image is longer than the Hub length limit of 25000 , so has been trimmed. The full description can be found at [ https://github.com/docker-library/docs/tree/master/nextcloud/README.md ] (https://github.com/docker-library/docs/tree/master/nextcloud/README.md). See also [ docker/hub-feedback#238 ] (https://github.com/docker/hub-feedback/issues/238) and [ docker/roadmap#475 ] (https://github.com/docker/roadmap/issues/475).
Markdown	Search Docker Hub CtrlK Help Back [Documentation⁠](https://docs.docker.com/docker-hub) [Forums⁠](https://forums.docker.com/c/docker-hub) [Contact support](https://hub.docker.com/support/contact) [System status⁠](https://www.dockerstatus.com/) System theme [Sign in](https://hub.docker.com/login)[Sign up](https://app.docker.com/signup) Back Back Help Back [Documentation⁠](https://docs.docker.com/docker-hub) [Forums⁠](https://forums.docker.com/c/docker-hub) [Contact support](https://hub.docker.com/support/contact) [System status⁠](https://www.dockerstatus.com/) System theme Docker Suite 1. [Explore](https://hub.docker.com/search) 2. / 3. [Official Images](https://hub.docker.com/search?badges=official) 4. / 5. nextcloud ## nextcloud Docker Official Image • 1B+ • 4\.5K Nextcloud manual docker image [Content management system](https://hub.docker.com/categories/content-management-system) [Overview](https://hub.docker.com/_/nextcloud/)[Tags](https://hub.docker.com/_/nextcloud/tags) # nextcloud Docker official image overview Note: the description for this image is longer than the Hub length limit of 25000, so has been trimmed. The full description can be found at [https://github.com/docker-library/docs/tree/master/nextcloud/README.md⁠](https://github.com/docker-library/docs/tree/master/nextcloud/README.md). See also [docker/hub-feedback\#238⁠](https://github.com/docker/hub-feedback/issues/238) and [docker/roadmap\#475⁠](https://github.com/docker/roadmap/issues/475). ### IMPORTANT NOTE ⚠️⚠️⚠️ This image is maintained by community volunteers and designed for expert use. For quick and easy deployment that supports the full set of Nextcloud Hub features, use the [Nextcloud All-in-One docker container⁠](https://github.com/nextcloud/all-in-one#nextcloud-all-in-one) maintained by Nextcloud GmbH. ### Quick reference - Maintained by: [the Nextcloud community⁠](https://github.com/nextcloud/docker) - Where to get help: [the Docker Community Slack⁠](https://dockr.ly/comm-slack), [Server Fault⁠](https://serverfault.com/help/on-topic), [Unix & Linux⁠](https://unix.stackexchange.com/help/on-topic), or [Stack Overflow⁠](https://stackoverflow.com/help/on-topic) ### Supported tags and respective `Dockerfile` links - [`32.0.8-apache`, `32.0-apache`, `32-apache`, `stable-apache`, `production-apache`, `32.0.8`, `32.0`, `32`, `stable`, `production`⁠](https://github.com/nextcloud/docker/blob/efa6ee645631d34047625a82dfddd083324628ef/32/apache/Dockerfile) - [`32.0.8-fpm`, `32.0-fpm`, `32-fpm`, `stable-fpm`, `production-fpm`⁠](https://github.com/nextcloud/docker/blob/efa6ee645631d34047625a82dfddd083324628ef/32/fpm/Dockerfile) - [`32.0.8-fpm-alpine`, `32.0-fpm-alpine`, `32-fpm-alpine`, `stable-fpm-alpine`, `production-fpm-alpine`⁠](https://github.com/nextcloud/docker/blob/efa6ee645631d34047625a82dfddd083324628ef/32/fpm-alpine/Dockerfile) - [`33.0.2-apache`, `33.0-apache`, `33-apache`, `apache`, `33.0.2`, `33.0`, `33`, `latest`⁠](https://github.com/nextcloud/docker/blob/efa6ee645631d34047625a82dfddd083324628ef/33/apache/Dockerfile) - [`33.0.2-fpm`, `33.0-fpm`, `33-fpm`, `fpm`⁠](https://github.com/nextcloud/docker/blob/efa6ee645631d34047625a82dfddd083324628ef/33/fpm/Dockerfile) - [`33.0.2-fpm-alpine`, `33.0-fpm-alpine`, `33-fpm-alpine`, `fpm-alpine`⁠](https://github.com/nextcloud/docker/blob/efa6ee645631d34047625a82dfddd083324628ef/33/fpm-alpine/Dockerfile) ### Quick reference (cont.) - Where to file issues: [https://github.com/nextcloud/docker/issues⁠](https://github.com/nextcloud/docker/issues?q=) - Supported architectures: ([more info⁠](https://github.com/docker-library/official-images#architectures-other-than-amd64)) [`amd64`](https://hub.docker.com/r/amd64/nextcloud/), [`arm32v5`](https://hub.docker.com/r/arm32v5/nextcloud/), [`arm32v6`](https://hub.docker.com/r/arm32v6/nextcloud/), [`arm32v7`](https://hub.docker.com/r/arm32v7/nextcloud/), [`arm64v8`](https://hub.docker.com/r/arm64v8/nextcloud/), [`i386`](https://hub.docker.com/r/i386/nextcloud/), [`ppc64le`](https://hub.docker.com/r/ppc64le/nextcloud/), [`riscv64`](https://hub.docker.com/r/riscv64/nextcloud/), [`s390x`](https://hub.docker.com/r/s390x/nextcloud/) - Published image artifact details: [repo-info repo's `repos/nextcloud/` directory⁠](https://github.com/docker-library/repo-info/blob/master/repos/nextcloud) ([history⁠](https://github.com/docker-library/repo-info/commits/master/repos/nextcloud)) (image metadata, transfer size, etc) - Image updates: [official-images repo's `library/nextcloud` label⁠](https://github.com/docker-library/official-images/issues?q=label%3Alibrary%2Fnextcloud) [official-images repo's `library/nextcloud` file⁠](https://github.com/docker-library/official-images/blob/master/library/nextcloud) ([history⁠](https://github.com/docker-library/official-images/commits/master/library/nextcloud)) - Source of this description: [docs repo's `nextcloud/` directory⁠](https://github.com/docker-library/docs/tree/master/nextcloud) ([history⁠](https://github.com/docker-library/docs/commits/master/nextcloud)) ### What is Nextcloud? A safe home for all your data. Access & share your files, calendars, contacts, mail & more from any device, on your terms. > [Nextcloud.com⁠](https://nextcloud.com/) This Docker micro-service image is developed and maintained by the Nextcloud community. Nextcloud GmbH does not offer support for this Docker image. When you are looking to get professional support, you can become an [enterprise⁠](https://nextcloud.com/enterprise/) customer or use [AIO⁠](https://github.com/nextcloud/all-in-one#nextcloud-all-in-one). ### How to use this image This image is designed to be used in a micro-service environment. There are two versions of the image you can choose from. The `apache` tag contains a full Nextcloud installation including an apache web server. It is designed to be easy to use and gets you running pretty fast. This is also the default for the `latest` tag and version tags that are not further specified. The second option is a `fpm` container. It is based on the [php-fpm](https://hub.docker.com/_/php/) image and runs a fastCGI-Process that serves your Nextcloud page. To use this image it must be combined with any webserver that can proxy the http requests to the FastCGI-port of the container. #### Using the apache image The apache image contains a webserver and exposes port 80. To start the container type: ``` $ docker run -d -p 8080:80 nextcloud ``` Copy Now you can access Nextcloud at [http://localhost:8080/⁠](http://localhost:8080/) from your host system. #### Using the fpm image To use the fpm image, you need an additional web server, such as [nginx⁠](https://docs.nextcloud.com/server/latest/admin_manual/installation/nginx.html), that can proxy http-request to the fpm-port of the container. For fpm connection this container exposes port 9000. In most cases, you might want to use another container or your host as proxy. If you use your host you can address your Nextcloud container directly on port 9000. If you use another container, make sure that you add them to the same docker network (via `docker run --network <NAME> ...` or a `compose.yaml` file). In both cases you don't want to map the fpm port to your host. ``` $ docker run -d nextcloud:fpm ``` Copy As the fastCGI-Process is not capable of serving static files (style sheets, images, ...), the webserver needs access to these files. This can be achieved with the `volumes-from` option. You can find more information in the Docker Compose section. #### Using an external database By default, this container uses SQLite for data storage but the Nextcloud setup wizard (appears on first run) allows connecting to an existing MySQL/MariaDB or PostgreSQL database. You can also link a database container, e. g. `--link my-mysql:mysql`, and then use `mysql` as the database host on setup. More info is in the Docker Compose section. #### Persistent data The Nextcloud installation and all data beyond what lives in the database (file uploads, etc.) are stored in the [unnamed docker volume⁠](https://docs.docker.com/storage/volumes/) volume `/var/www/html`. The docker daemon will store that data within the docker directory `/var/lib/docker/volumes/...`. That means your data is saved even if the container crashes, is stopped or deleted. A named Docker volume or a mounted host directory should be used for upgrades and backups. To achieve this, you need one volume for your database container and one for Nextcloud. Nextcloud: - `/var/www/html/` folder where all Nextcloud data lives ``` $ docker run -d \ -v nextcloud:/var/www/html \ nextcloud ``` Copy Database: - `/var/lib/mysql` MySQL / MariaDB Data - `/var/lib/postgresql/data` PostgreSQL Data ``` $ docker run -d \ -v db:/var/lib/mysql \ mariadb:10.6 ``` Copy ##### Additional volumes If you want to get fine grained access to your individual files, you can mount additional volumes for data, config, your theme and custom apps. The `data`, `config` files are stored in respective subfolders inside `/var/www/html/`. The apps are split into core `apps` (which are shipped with Nextcloud and you don't need to take care of) and a `custom_apps` folder. If you use a custom theme it would go into the `themes` subfolder. Overview of the folders that can be mounted as volumes: - `/var/www/html` Main folder, needed for updating - `/var/www/html/custom_apps` installed / modified apps - `/var/www/html/config` local configuration - `/var/www/html/data` the actual data of your Nextcloud - `/var/www/html/themes/<YOUR_CUSTOM_THEME>` theming/branding If you want to use named volumes for all of these, it would look like this: ``` $ docker run -d \ -v nextcloud:/var/www/html \ -v apps:/var/www/html/custom_apps \ -v config:/var/www/html/config \ -v data:/var/www/html/data \ -v theme:/var/www/html/themes/<YOUR_CUSTOM_THEME> \ nextcloud ``` Copy ##### Custom volumes If mounting additional volumes under `/var/www/html`, you should consider: - Confirming that [upgrade.exclude⁠](https://github.com/nextcloud/docker/blob/master/upgrade.exclude) contains the files and folders that should persist during installation and upgrades; or - Mounting storage volumes to locations outside of `/var/www/html`. > You should note that data inside the main folder (`/var/www/html`) will be overridden/removed during installation and upgrades, unless listed in [upgrade.exclude⁠](https://github.com/nextcloud/docker/blob/master/upgrade.exclude). The additional volumes officially supported are already in that list, but custom volumes will need to be added by you. We suggest mounting custom storage volumes outside of `/var/www/html` and if possible read-only so that making this adjustment is unnecessary. If you must do so, however, you may build a custom image with a modified `/upgrade.exclude` file that incorporates your custom volume(s). #### Using the Nextcloud command-line interface To use the [Nextcloud command-line interface⁠](https://docs.nextcloud.com/server/latest/admin_manual/configuration_server/occ_command.html) (aka. `occ` command): ``` $ docker exec --user www-data CONTAINER_ID php occ ``` Copy or for `docker compose`: ``` $ docker compose exec --user www-data app php occ ``` Copy #### Auto configuration via environment variables The Nextcloud image supports auto configuration via environment variables. You can preconfigure everything that is asked on the install page on first run. To enable auto configuration, set your database connection via the following environment variables. You must specify all of the environment variables for a given database or the database environment variables defaults to SQLITE. ONLY use one database type\! SQLite: - `SQLITE_DATABASE` Name of the database using sqlite MYSQL/MariaDB: - `MYSQL_DATABASE` Name of the database using mysql / mariadb. - `MYSQL_USER` Username for the database using mysql / mariadb. - `MYSQL_PASSWORD` Password for the database user using mysql / mariadb. - `MYSQL_HOST` Hostname of the database server using mysql / mariadb. PostgreSQL: - `POSTGRES_DB` Name of the database using postgres. - `POSTGRES_USER` Username for the database using postgres. - `POSTGRES_PASSWORD` Password for the database user using postgres. - `POSTGRES_HOST` Hostname of the database server using postgres. As an alternative to passing sensitive information via environment variables, `_FILE` may be appended to the previously listed environment variables, causing the initialization script to load the values for those variables from files present in the container. See [Docker secrets](https://hub.docker.com/_/nextcloud/#docker-secrets) section below. If you set any group of values (i.e. all of `MYSQL_DATABASE`, `MYSQL_USER`, `MYSQL_PASSWORD`, `MYSQL_HOST`), they will not be asked in the install page on first run. With a complete configuration by using all variables for your database type, you can additionally configure your Nextcloud instance by setting admin user and password (only works if you set both): - `NEXTCLOUD_ADMIN_USER` Name of the Nextcloud admin user. - `NEXTCLOUD_ADMIN_PASSWORD` Password for the Nextcloud admin user. If you want, you can set the data directory, otherwise default value will be used. - `NEXTCLOUD_DATA_DIR` (default: `/var/www/html/data`) Configures the data directory where nextcloud stores all files from the users. One or more trusted domains can be set through environment variable, too. They will be added to the configuration after install. - `NEXTCLOUD_TRUSTED_DOMAINS` (not set by default) Optional space-separated list of domains The install and update script is only triggered when a default command is used (`apache-foreground` or `php-fpm`). If you use a custom command you have to enable the install / update with - `NEXTCLOUD_UPDATE` (default: `0`) You might want to make sure the htaccess is up to date after each container update. Especially on multiple swarm nodes as any discrepancy will make your server unusable. - `NEXTCLOUD_INIT_HTACCESS` (not set by default) Set it to true to enable run `occ maintenance:update:htaccess` after container initialization. If you want to use Redis you have to create a separate [Redis](https://hub.docker.com/_/redis/) container in your setup / in your Compose file. To inform Nextcloud about the Redis container, pass in the following parameters: - `REDIS_HOST` (not set by default) Name of Redis container - `REDIS_HOST_PORT` (default: `6379`) Optional port for Redis, only use for external Redis servers that run on non-standard ports. - `REDIS_HOST_PASSWORD` (not set by default) Redis password The use of Redis is recommended to prevent file locking problems. See the examples for further instructions. To use an external SMTP server, you have to provide the connection details. To configure Nextcloud to use SMTP add: - `SMTP_HOST` (not set by default): The hostname of the SMTP server. - `SMTP_SECURE` (empty by default): Set to `ssl` to use SSL, or `tls` to use STARTTLS. - `SMTP_PORT` (default: `465` for SSL and `25` for non-secure connections): Optional port for the SMTP connection. Use `587` for an alternative port for STARTTLS. - `SMTP_AUTHTYPE` (default: `LOGIN`): The method used for authentication. Use `PLAIN` if no authentication is required. - `SMTP_NAME` (empty by default): The username for the authentication. - `SMTP_PASSWORD` (empty by default): The password for the authentication. - `MAIL_FROM_ADDRESS` (not set by default): Set the local-part for the 'from' field in the emails sent by Nextcloud. - `MAIL_DOMAIN` (not set by default): Set a different domain for the emails than the domain where Nextcloud is installed. At least `SMTP_HOST`, `MAIL_FROM_ADDRESS` and `MAIL_DOMAIN` must be set for the configurations to be applied. Check the [Nextcloud documentation⁠](https://docs.nextcloud.com/server/latest/admin_manual/configuration_server/email_configuration.html) for other values to configure SMTP. To use an external S3 compatible object store as primary storage, set the following variables: - `OBJECTSTORE_S3_BUCKET`: The name of the bucket that Nextcloud should store the data in - `OBJECTSTORE_S3_REGION`: The region that the S3 bucket resides in - `OBJECTSTORE_S3_HOST`: The hostname of the object storage server - `OBJECTSTORE_S3_PORT`: The port that the object storage server is being served over - `OBJECTSTORE_S3_KEY`: AWS style access key - `OBJECTSTORE_S3_SECRET`: AWS style secret access key - `OBJECTSTORE_S3_STORAGE_CLASS`: The storage class to use when adding objects to the bucket - `OBJECTSTORE_S3_SSL` (default: `true`): Whether or not SSL/TLS should be used to communicate with object storage server - `OBJECTSTORE_S3_USEPATH_STYLE` (default: `false`): Not required for AWS S3 - `OBJECTSTORE_S3_LEGACYAUTH` (default: `false`): Not required for AWS S3 - `OBJECTSTORE_S3_OBJECT_PREFIX` (default: `urn:oid:`): Prefix to prepend to the fileid - `OBJECTSTORE_S3_AUTOCREATE` (default: `true`): Create the container if it does not exist - `OBJECTSTORE_S3_SSE_C_KEY` (not set by default): Base64 encoded key with a maximum length of 32 bytes for server side encryption (SSE-C) Check the [Nextcloud documentation⁠](https://docs.nextcloud.com/server/latest/admin_manual/configuration_files/primary_storage.html#simple-storage-service-s3) for more information. To use an external OpenStack Swift object store as primary storage, set the following variables: - `OBJECTSTORE_SWIFT_URL`: The Swift identity (Keystone) endpoint - `OBJECTSTORE_SWIFT_AUTOCREATE` (default: `false`): Whether or not Nextcloud should automatically create the Swift container - `OBJECTSTORE_SWIFT_USER_NAME`: Swift username - `OBJECTSTORE_SWIFT_USER_PASSWORD`: Swift user password - `OBJECTSTORE_SWIFT_USER_DOMAIN` (default: `Default`): Swift user domain - `OBJECTSTORE_SWIFT_PROJECT_NAME`: OpenStack project name - `OBJECTSTORE_SWIFT_PROJECT_DOMAIN` (default: `Default`): OpenStack project domain - `OBJECTSTORE_SWIFT_SERVICE_NAME` (default: `swift`): Swift service name - `OBJECTSTORE_SWIFT_REGION`: Swift endpoint region - `OBJECTSTORE_SWIFT_CONTAINER_NAME`: Swift container (bucket) that Nextcloud should store the data in Check the [Nextcloud documentation⁠](https://docs.nextcloud.com/server/latest/admin_manual/configuration_files/primary_storage.html#openstack-swift) for more information. To customize other PHP limits you can simply change the following variables: - `PHP_MEMORY_LIMIT` (default `512M`) This sets the maximum amount of memory in bytes that a script is allowed to allocate. This is meant to help prevent poorly written scripts from eating up all available memory but it can prevent normal operation if set too tight. - `PHP_UPLOAD_LIMIT` (default `512M`) This sets the upload limit (`post_max_size` and `upload_max_filesize`) for big files. Note that you may have to change other limits depending on your client, webserver or operating system. Check the [Nextcloud documentation⁠](https://docs.nextcloud.com/server/latest/admin_manual/configuration_files/big_file_upload_configuration.html) for more information. To customize Apache max file upload limit you can change the following variable: - `APACHE_BODY_LIMIT` (default `1073741824` \[1GiB\]) This restricts the total size of the HTTP request body sent from the client. It specifies the number of bytes that are allowed in a request body. A value of 0 means unlimited. Check the [Nextcloud documentation⁠](https://docs.nextcloud.com/server/latest/admin_manual/configuration_files/big_file_upload_configuration.html#apache) for more information. #### Auto configuration via hook folders There are 5 hooks - `pre-installation` Executed before the Nextcloud is installed/initiated - `post-installation` Executed after the Nextcloud is installed/initiated - `pre-upgrade` Executed before the Nextcloud is upgraded - `post-upgrade` Executed after the Nextcloud is upgraded - `before-starting` Executed before the Nextcloud starts To use the hooks triggered by the `entrypoint` script, either - Added your script(s) to the individual of the hook folder(s), which are located at the path `/docker-entrypoint-hooks.d` in the container - Use volume(s) if you want to use script from the host system inside the container, see example. Note: Only the script(s) located in a hook folder (not sub-folders), ending with `.sh` and marked as executable, will be executed. Example: Mount using volumes ``` ... app: image: nextcloud:stable volumes: - ./app-hooks/pre-installation:/docker-entrypoint-hooks.d/pre-installation - ./app-hooks/post-installation:/docker-entrypoint-hooks.d/post-installation - ./app-hooks/pre-upgrade:/docker-entrypoint-hooks.d/pre-upgrade - ./app-hooks/post-upgrade:/docker-entrypoint-hooks.d/post-upgrade - ./app-hooks/before-starting:/docker-entrypoint-hooks.d/before-starting ... ``` Copy #### Using the apache image behind a reverse proxy and auto configure server host and protocol The apache image will replace the remote addr (IP address visible to Nextcloud) with the IP address from `X-Real-IP` if the request is coming from a proxy in `10.0.0.0/8`, `172.16.0.0/12` or `192.168.0.0/16` by default. If you want Nextcloud to pick up the server host (`HTTP_X_FORWARDED_HOST`), protocol (`HTTP_X_FORWARDED_PROTO`) and client IP (`HTTP_X_FORWARDED_FOR`) from a trusted proxy, then disable rewrite IP and add the reverse proxy's IP address to `TRUSTED_PROXIES`. - `APACHE_DISABLE_REWRITE_IP` (not set by default): Set to 1 to disable rewrite IP. - `TRUSTED_PROXIES` (empty by default): A space-separated list of trusted proxies. CIDR notation is supported for IPv4. If the `TRUSTED_PROXIES` approach does not work for you, try using fixed values for overwrite parameters. - `OVERWRITEHOST` (empty by default): Set the hostname of the proxy. Can also specify a port. - `OVERWRITEPROTOCOL` (empty by default): Set the protocol of the proxy, http or https. - `OVERWRITECLIURL` (empty by default): Set the cli url of the proxy (e.g. [https://mydnsname.example.com⁠](https://mydnsname.example.com/) ) - `OVERWRITEWEBROOT` (empty by default): Set the absolute path of the proxy. - `OVERWRITECONDADDR` (empty by default): Regex to overwrite the values dependent on the remote address. Check the [Nexcloud documentation⁠](https://docs.nextcloud.com/server/latest/admin_manual/configuration_server/reverse_proxy_configuration.html) for more details. Keep in mind that once set, removing these environment variables won't remove these values from the configuration file, due to how Nextcloud merges configuration files together. ### Running this image with Docker Compose The easiest way to get a fully featured and functional setup is using a `compose.yaml` file. There are too many different possibilities to setup your system, so here are only some examples of what you have to look for. At first, make sure you have chosen the right base image (fpm or apache) and added features you wanted (see below). In every case, you would want to add a database container and docker volumes to get easy access to your persistent data. When you want to have your server reachable from the internet, adding HTTPS-encryption is mandatory! See below for more information. #### Base version - apache This version will use the apache image and add a mariaDB container. The volumes are set to keep your data persistent. This setup provides no ssl encryption and is intended to run behind a proxy. Make sure to pass in values for `MYSQL_ROOT_PASSWORD` and `MYSQL_PASSWORD` variables before you run this setup. ``` volumes: nextcloud: db: services: db: image: mariadb:10.6 restart: always command: --transaction-isolation=READ-COMMITTED --log-bin=binlog --binlog-format=ROW volumes: - db:/var/lib/mysql environment: - MYSQL_ROOT_PASSWORD= - MYSQL_PASSWORD= - MYSQL_DATABASE=nextcloud - MYSQL_USER=nextcloud app: image: nextcloud restart: always ports: - 8080:80 links: - db volumes: - nextcloud:/var/www/html environment: - MYSQL_PASSWORD= - MYSQL_DATABASE=nextcloud - MYSQL_USER=nextcloud - MYSQL_HOST=db ``` Copy Then run `docker compose up -d`, now you can access Nextcloud at [http://localhost:8080/⁠](http://localhost:8080/) from your host system. #### Base version - FPM When using the FPM image, you need another container that acts as web server on port 80 and proxies the requests to the Nextcloud container. In this example a simple nginx container is combined with the Nextcloud-fpm image and a MariaDB database container. The data is stored in docker volumes. The nginx container also needs access to static files from your Nextcloud installation. It gets access to all the volumes mounted to Nextcloud via the `volumes_from` option. The configuration for nginx is stored in the configuration file `nginx.conf`, that is mounted into the container. An example can be found in the examples section [here⁠](https://github.com/nextcloud/docker/tree/master/.examples). As this setup does not include encryption, it should be run behind a proxy. Make sure to pass in values for `MYSQL_ROOT_PASSWORD` and `MYSQL_PASSWORD` variables before you run this setup. ``` volumes: nextcloud: db: services: db: image: mariadb:10.6 restart: always command: --transaction-isolation=READ-COMMITTED --log-bin=binlog --binlog-format=ROW volumes: - db:/var/lib/mysql environment: - MYSQL_ROOT_PASSWORD= - MYSQL_PASSWORD= - MYSQL_DATABASE=nextcloud - MYSQL_USER=nextcloud ... Note: the description for this image is longer than the Hub length limit of 25000, so has been trimmed. The full description can be found at [https://github.com/docker-library/docs/tree/master/nextcloud/README.md](https://github.com/docker-library/docs/tree/master/nextcloud/README.md). See also [docker/hub-feedback#238](https://github.com/docker/hub-feedback/issues/238) and [docker/roadmap#475](https://github.com/docker/roadmap/issues/475). ``` Copy ### Tag summary Recent tags stable-fpm-alpine Recent tags Content type Image Digest sha256:dde27986e… Size 361\.4 MB Last updated 3 days ago ``` docker pull nextcloud:stable-fpm-alpine ``` Copy ### This week's pulls Pulls: 580,141 Mar 23 to Mar 29 [Learn more⁠](https://www.docker.com/partners/publisher-insights/) ### About Official Images Docker Official Images are a curated set of Docker open source and drop-in solution repositories. ###### Why Official Images? These images have clear documentation, promote best practices, and are designed for the most common use cases. Why[Overview](https://www.docker.com/why-docker)[What is a Container](https://www.docker.com/resources/what-container) Products[Product Overview](https://www.docker.com/products)Product Offerings[Docker Desktop](https://www.docker.com/products/docker-desktop)[Docker Hub](https://www.docker.com/products/docker-hub)Features[Container Runtime](https://www.docker.com/products/container-runtime)[Developer Tools](https://www.docker.com/products/developer-tools)[Docker App](https://www.docker.com/products/docker-app)[Kubernetes](https://www.docker.com/products/kubernetes) Developers[Getting Started](https://docs.docker.com/get-started)[Play with Docker](https://www.docker.com/play-with-docker)[Community](https://www.docker.com/docker-community)[Open Source](https://www.docker.com/open-source)[Documentation](https://www.docker.com/docs) Company[About Us](https://www.docker.com/company)[Resources](https://www.docker.com/resources)[Blog](https://www.docker.com/blog/)[Customers](https://www.docker.com/customers)[Partners](https://www.docker.com/partners)[Newsroom](https://www.docker.com/company/newsroom)[Events and Webinars](https://www.docker.com/events-and-webinars)[Careers](https://www.docker.com/careers)[Contact Us](https://www.docker.com/company/contact) [System Status⁠](https://www.dockerstatus.com/) *** © 2026 Docker, Inc. All rights reserved. \\| [Terms of Service](https://www.docker.com/legal/docker-terms-service) \\| [Subscription Service Agreement](https://www.docker.com/legal/docker-subscription-service-agreement) \\| [Privacy](https://www.docker.com/legal/privacy) \\| [Legal](https://www.docker.com/legal) Cookies Settings Back - System theme - Light theme - Dark theme Back - System theme - Light theme - Dark theme Back [Docker Home Explore and manage your Docker experience.](https://app.docker.com/) [Docker Admin Console Manage users, control access, & set policies.](https://app.docker.com/admin) [Docker Hub Find and share images with your team.](https://hub.docker.com/) [Docker Scout Secure your supply chain at every level.](https://scout.docker.com/) [Docker Desktop Local development, simplified.](https://hub.docker.com/open-desktop) [Docker Build Cloud Speed up your builds.](https://app.docker.com/build) [Testcontainers Cloud New Run integration tests with real dependencies.](https://app.testcontainers.cloud/)
Readable Markdown	Note: the description for this image is longer than the Hub length limit of 25000, so has been trimmed. The full description can be found at [https://github.com/docker-library/docs/tree/master/nextcloud/README.md⁠](https://github.com/docker-library/docs/tree/master/nextcloud/README.md). See also [docker/hub-feedback\#238⁠](https://github.com/docker/hub-feedback/issues/238) and [docker/roadmap\#475⁠](https://github.com/docker/roadmap/issues/475). ### IMPORTANT NOTE ⚠️⚠️⚠️ This image is maintained by community volunteers and designed for expert use. For quick and easy deployment that supports the full set of Nextcloud Hub features, use the [Nextcloud All-in-One docker container⁠](https://github.com/nextcloud/all-in-one#nextcloud-all-in-one) maintained by Nextcloud GmbH. ### Quick reference - Maintained by: [the Nextcloud community⁠](https://github.com/nextcloud/docker) - Where to get help: [the Docker Community Slack⁠](https://dockr.ly/comm-slack), [Server Fault⁠](https://serverfault.com/help/on-topic), [Unix & Linux⁠](https://unix.stackexchange.com/help/on-topic), or [Stack Overflow⁠](https://stackoverflow.com/help/on-topic) ### Supported tags and respective `Dockerfile` links - [`32.0.8-apache`, `32.0-apache`, `32-apache`, `stable-apache`, `production-apache`, `32.0.8`, `32.0`, `32`, `stable`, `production`⁠](https://github.com/nextcloud/docker/blob/efa6ee645631d34047625a82dfddd083324628ef/32/apache/Dockerfile) - [`32.0.8-fpm`, `32.0-fpm`, `32-fpm`, `stable-fpm`, `production-fpm`⁠](https://github.com/nextcloud/docker/blob/efa6ee645631d34047625a82dfddd083324628ef/32/fpm/Dockerfile) - [`32.0.8-fpm-alpine`, `32.0-fpm-alpine`, `32-fpm-alpine`, `stable-fpm-alpine`, `production-fpm-alpine`⁠](https://github.com/nextcloud/docker/blob/efa6ee645631d34047625a82dfddd083324628ef/32/fpm-alpine/Dockerfile) - [`33.0.2-apache`, `33.0-apache`, `33-apache`, `apache`, `33.0.2`, `33.0`, `33`, `latest`⁠](https://github.com/nextcloud/docker/blob/efa6ee645631d34047625a82dfddd083324628ef/33/apache/Dockerfile) - [`33.0.2-fpm`, `33.0-fpm`, `33-fpm`, `fpm`⁠](https://github.com/nextcloud/docker/blob/efa6ee645631d34047625a82dfddd083324628ef/33/fpm/Dockerfile) - [`33.0.2-fpm-alpine`, `33.0-fpm-alpine`, `33-fpm-alpine`, `fpm-alpine`⁠](https://github.com/nextcloud/docker/blob/efa6ee645631d34047625a82dfddd083324628ef/33/fpm-alpine/Dockerfile) ### Quick reference (cont.) - Where to file issues: [https://github.com/nextcloud/docker/issues⁠](https://github.com/nextcloud/docker/issues?q=) - Supported architectures: ([more info⁠](https://github.com/docker-library/official-images#architectures-other-than-amd64)) [`amd64`](https://hub.docker.com/r/amd64/nextcloud/), [`arm32v5`](https://hub.docker.com/r/arm32v5/nextcloud/), [`arm32v6`](https://hub.docker.com/r/arm32v6/nextcloud/), [`arm32v7`](https://hub.docker.com/r/arm32v7/nextcloud/), [`arm64v8`](https://hub.docker.com/r/arm64v8/nextcloud/), [`i386`](https://hub.docker.com/r/i386/nextcloud/), [`ppc64le`](https://hub.docker.com/r/ppc64le/nextcloud/), [`riscv64`](https://hub.docker.com/r/riscv64/nextcloud/), [`s390x`](https://hub.docker.com/r/s390x/nextcloud/) - Published image artifact details: [repo-info repo's `repos/nextcloud/` directory⁠](https://github.com/docker-library/repo-info/blob/master/repos/nextcloud) ([history⁠](https://github.com/docker-library/repo-info/commits/master/repos/nextcloud)) (image metadata, transfer size, etc) - Image updates: [official-images repo's `library/nextcloud` label⁠](https://github.com/docker-library/official-images/issues?q=label%3Alibrary%2Fnextcloud) [official-images repo's `library/nextcloud` file⁠](https://github.com/docker-library/official-images/blob/master/library/nextcloud) ([history⁠](https://github.com/docker-library/official-images/commits/master/library/nextcloud)) - Source of this description: [docs repo's `nextcloud/` directory⁠](https://github.com/docker-library/docs/tree/master/nextcloud) ([history⁠](https://github.com/docker-library/docs/commits/master/nextcloud)) ### What is Nextcloud? A safe home for all your data. Access & share your files, calendars, contacts, mail & more from any device, on your terms. This Docker micro-service image is developed and maintained by the Nextcloud community. Nextcloud GmbH does not offer support for this Docker image. When you are looking to get professional support, you can become an [enterprise⁠](https://nextcloud.com/enterprise/) customer or use [AIO⁠](https://github.com/nextcloud/all-in-one#nextcloud-all-in-one). ### How to use this image This image is designed to be used in a micro-service environment. There are two versions of the image you can choose from. The `apache` tag contains a full Nextcloud installation including an apache web server. It is designed to be easy to use and gets you running pretty fast. This is also the default for the `latest` tag and version tags that are not further specified. The second option is a `fpm` container. It is based on the [php-fpm](https://hub.docker.com/_/php/) image and runs a fastCGI-Process that serves your Nextcloud page. To use this image it must be combined with any webserver that can proxy the http requests to the FastCGI-port of the container. #### Using the apache image The apache image contains a webserver and exposes port 80. To start the container type: ``` $ docker run -d -p 8080:80 nextcloud ``` Now you can access Nextcloud at [http://localhost:8080/⁠](http://localhost:8080/) from your host system. #### Using the fpm image To use the fpm image, you need an additional web server, such as [nginx⁠](https://docs.nextcloud.com/server/latest/admin_manual/installation/nginx.html), that can proxy http-request to the fpm-port of the container. For fpm connection this container exposes port 9000. In most cases, you might want to use another container or your host as proxy. If you use your host you can address your Nextcloud container directly on port 9000. If you use another container, make sure that you add them to the same docker network (via `docker run --network <NAME> ...` or a `compose.yaml` file). In both cases you don't want to map the fpm port to your host. ``` $ docker run -d nextcloud:fpm ``` As the fastCGI-Process is not capable of serving static files (style sheets, images, ...), the webserver needs access to these files. This can be achieved with the `volumes-from` option. You can find more information in the Docker Compose section. #### Using an external database By default, this container uses SQLite for data storage but the Nextcloud setup wizard (appears on first run) allows connecting to an existing MySQL/MariaDB or PostgreSQL database. You can also link a database container, e. g. `--link my-mysql:mysql`, and then use `mysql` as the database host on setup. More info is in the Docker Compose section. #### Persistent data The Nextcloud installation and all data beyond what lives in the database (file uploads, etc.) are stored in the [unnamed docker volume⁠](https://docs.docker.com/storage/volumes/) volume `/var/www/html`. The docker daemon will store that data within the docker directory `/var/lib/docker/volumes/...`. That means your data is saved even if the container crashes, is stopped or deleted. A named Docker volume or a mounted host directory should be used for upgrades and backups. To achieve this, you need one volume for your database container and one for Nextcloud. Nextcloud: - `/var/www/html/` folder where all Nextcloud data lives ``` $ docker run -d \ -v nextcloud:/var/www/html \ nextcloud ``` Database: - `/var/lib/mysql` MySQL / MariaDB Data - `/var/lib/postgresql/data` PostgreSQL Data ``` $ docker run -d \ -v db:/var/lib/mysql \ mariadb:10.6 ``` ##### Additional volumes If you want to get fine grained access to your individual files, you can mount additional volumes for data, config, your theme and custom apps. The `data`, `config` files are stored in respective subfolders inside `/var/www/html/`. The apps are split into core `apps` (which are shipped with Nextcloud and you don't need to take care of) and a `custom_apps` folder. If you use a custom theme it would go into the `themes` subfolder. Overview of the folders that can be mounted as volumes: - `/var/www/html` Main folder, needed for updating - `/var/www/html/custom_apps` installed / modified apps - `/var/www/html/config` local configuration - `/var/www/html/data` the actual data of your Nextcloud - `/var/www/html/themes/<YOUR_CUSTOM_THEME>` theming/branding If you want to use named volumes for all of these, it would look like this: ``` $ docker run -d \ -v nextcloud:/var/www/html \ -v apps:/var/www/html/custom_apps \ -v config:/var/www/html/config \ -v data:/var/www/html/data \ -v theme:/var/www/html/themes/<YOUR_CUSTOM_THEME> \ nextcloud ``` ##### Custom volumes If mounting additional volumes under `/var/www/html`, you should consider: - Confirming that [upgrade.exclude⁠](https://github.com/nextcloud/docker/blob/master/upgrade.exclude) contains the files and folders that should persist during installation and upgrades; or - Mounting storage volumes to locations outside of `/var/www/html`. > You should note that data inside the main folder (`/var/www/html`) will be overridden/removed during installation and upgrades, unless listed in [upgrade.exclude⁠](https://github.com/nextcloud/docker/blob/master/upgrade.exclude). The additional volumes officially supported are already in that list, but custom volumes will need to be added by you. We suggest mounting custom storage volumes outside of `/var/www/html` and if possible read-only so that making this adjustment is unnecessary. If you must do so, however, you may build a custom image with a modified `/upgrade.exclude` file that incorporates your custom volume(s). #### Using the Nextcloud command-line interface To use the [Nextcloud command-line interface⁠](https://docs.nextcloud.com/server/latest/admin_manual/configuration_server/occ_command.html) (aka. `occ` command): ``` $ docker exec --user www-data CONTAINER_ID php occ ``` or for `docker compose`: ``` $ docker compose exec --user www-data app php occ ``` #### Auto configuration via environment variables The Nextcloud image supports auto configuration via environment variables. You can preconfigure everything that is asked on the install page on first run. To enable auto configuration, set your database connection via the following environment variables. You must specify all of the environment variables for a given database or the database environment variables defaults to SQLITE. ONLY use one database type\! SQLite: - `SQLITE_DATABASE` Name of the database using sqlite MYSQL/MariaDB: - `MYSQL_DATABASE` Name of the database using mysql / mariadb. - `MYSQL_USER` Username for the database using mysql / mariadb. - `MYSQL_PASSWORD` Password for the database user using mysql / mariadb. - `MYSQL_HOST` Hostname of the database server using mysql / mariadb. PostgreSQL: - `POSTGRES_DB` Name of the database using postgres. - `POSTGRES_USER` Username for the database using postgres. - `POSTGRES_PASSWORD` Password for the database user using postgres. - `POSTGRES_HOST` Hostname of the database server using postgres. As an alternative to passing sensitive information via environment variables, `_FILE` may be appended to the previously listed environment variables, causing the initialization script to load the values for those variables from files present in the container. See [Docker secrets](https://hub.docker.com/_/nextcloud/#docker-secrets) section below. If you set any group of values (i.e. all of `MYSQL_DATABASE`, `MYSQL_USER`, `MYSQL_PASSWORD`, `MYSQL_HOST`), they will not be asked in the install page on first run. With a complete configuration by using all variables for your database type, you can additionally configure your Nextcloud instance by setting admin user and password (only works if you set both): - `NEXTCLOUD_ADMIN_USER` Name of the Nextcloud admin user. - `NEXTCLOUD_ADMIN_PASSWORD` Password for the Nextcloud admin user. If you want, you can set the data directory, otherwise default value will be used. - `NEXTCLOUD_DATA_DIR` (default: `/var/www/html/data`) Configures the data directory where nextcloud stores all files from the users. One or more trusted domains can be set through environment variable, too. They will be added to the configuration after install. - `NEXTCLOUD_TRUSTED_DOMAINS` (not set by default) Optional space-separated list of domains The install and update script is only triggered when a default command is used (`apache-foreground` or `php-fpm`). If you use a custom command you have to enable the install / update with - `NEXTCLOUD_UPDATE` (default: `0`) You might want to make sure the htaccess is up to date after each container update. Especially on multiple swarm nodes as any discrepancy will make your server unusable. - `NEXTCLOUD_INIT_HTACCESS` (not set by default) Set it to true to enable run `occ maintenance:update:htaccess` after container initialization. If you want to use Redis you have to create a separate [Redis](https://hub.docker.com/_/redis/) container in your setup / in your Compose file. To inform Nextcloud about the Redis container, pass in the following parameters: - `REDIS_HOST` (not set by default) Name of Redis container - `REDIS_HOST_PORT` (default: `6379`) Optional port for Redis, only use for external Redis servers that run on non-standard ports. - `REDIS_HOST_PASSWORD` (not set by default) Redis password The use of Redis is recommended to prevent file locking problems. See the examples for further instructions. To use an external SMTP server, you have to provide the connection details. To configure Nextcloud to use SMTP add: - `SMTP_HOST` (not set by default): The hostname of the SMTP server. - `SMTP_SECURE` (empty by default): Set to `ssl` to use SSL, or `tls` to use STARTTLS. - `SMTP_PORT` (default: `465` for SSL and `25` for non-secure connections): Optional port for the SMTP connection. Use `587` for an alternative port for STARTTLS. - `SMTP_AUTHTYPE` (default: `LOGIN`): The method used for authentication. Use `PLAIN` if no authentication is required. - `SMTP_NAME` (empty by default): The username for the authentication. - `SMTP_PASSWORD` (empty by default): The password for the authentication. - `MAIL_FROM_ADDRESS` (not set by default): Set the local-part for the 'from' field in the emails sent by Nextcloud. - `MAIL_DOMAIN` (not set by default): Set a different domain for the emails than the domain where Nextcloud is installed. At least `SMTP_HOST`, `MAIL_FROM_ADDRESS` and `MAIL_DOMAIN` must be set for the configurations to be applied. Check the [Nextcloud documentation⁠](https://docs.nextcloud.com/server/latest/admin_manual/configuration_server/email_configuration.html) for other values to configure SMTP. To use an external S3 compatible object store as primary storage, set the following variables: - `OBJECTSTORE_S3_BUCKET`: The name of the bucket that Nextcloud should store the data in - `OBJECTSTORE_S3_REGION`: The region that the S3 bucket resides in - `OBJECTSTORE_S3_HOST`: The hostname of the object storage server - `OBJECTSTORE_S3_PORT`: The port that the object storage server is being served over - `OBJECTSTORE_S3_KEY`: AWS style access key - `OBJECTSTORE_S3_SECRET`: AWS style secret access key - `OBJECTSTORE_S3_STORAGE_CLASS`: The storage class to use when adding objects to the bucket - `OBJECTSTORE_S3_SSL` (default: `true`): Whether or not SSL/TLS should be used to communicate with object storage server - `OBJECTSTORE_S3_USEPATH_STYLE` (default: `false`): Not required for AWS S3 - `OBJECTSTORE_S3_LEGACYAUTH` (default: `false`): Not required for AWS S3 - `OBJECTSTORE_S3_OBJECT_PREFIX` (default: `urn:oid:`): Prefix to prepend to the fileid - `OBJECTSTORE_S3_AUTOCREATE` (default: `true`): Create the container if it does not exist - `OBJECTSTORE_S3_SSE_C_KEY` (not set by default): Base64 encoded key with a maximum length of 32 bytes for server side encryption (SSE-C) Check the [Nextcloud documentation⁠](https://docs.nextcloud.com/server/latest/admin_manual/configuration_files/primary_storage.html#simple-storage-service-s3) for more information. To use an external OpenStack Swift object store as primary storage, set the following variables: - `OBJECTSTORE_SWIFT_URL`: The Swift identity (Keystone) endpoint - `OBJECTSTORE_SWIFT_AUTOCREATE` (default: `false`): Whether or not Nextcloud should automatically create the Swift container - `OBJECTSTORE_SWIFT_USER_NAME`: Swift username - `OBJECTSTORE_SWIFT_USER_PASSWORD`: Swift user password - `OBJECTSTORE_SWIFT_USER_DOMAIN` (default: `Default`): Swift user domain - `OBJECTSTORE_SWIFT_PROJECT_NAME`: OpenStack project name - `OBJECTSTORE_SWIFT_PROJECT_DOMAIN` (default: `Default`): OpenStack project domain - `OBJECTSTORE_SWIFT_SERVICE_NAME` (default: `swift`): Swift service name - `OBJECTSTORE_SWIFT_REGION`: Swift endpoint region - `OBJECTSTORE_SWIFT_CONTAINER_NAME`: Swift container (bucket) that Nextcloud should store the data in Check the [Nextcloud documentation⁠](https://docs.nextcloud.com/server/latest/admin_manual/configuration_files/primary_storage.html#openstack-swift) for more information. To customize other PHP limits you can simply change the following variables: - `PHP_MEMORY_LIMIT` (default `512M`) This sets the maximum amount of memory in bytes that a script is allowed to allocate. This is meant to help prevent poorly written scripts from eating up all available memory but it can prevent normal operation if set too tight. - `PHP_UPLOAD_LIMIT` (default `512M`) This sets the upload limit (`post_max_size` and `upload_max_filesize`) for big files. Note that you may have to change other limits depending on your client, webserver or operating system. Check the [Nextcloud documentation⁠](https://docs.nextcloud.com/server/latest/admin_manual/configuration_files/big_file_upload_configuration.html) for more information. To customize Apache max file upload limit you can change the following variable: - `APACHE_BODY_LIMIT` (default `1073741824` \[1GiB\]) This restricts the total size of the HTTP request body sent from the client. It specifies the number of bytes that are allowed in a request body. A value of 0 means unlimited. Check the [Nextcloud documentation⁠](https://docs.nextcloud.com/server/latest/admin_manual/configuration_files/big_file_upload_configuration.html#apache) for more information. #### Auto configuration via hook folders There are 5 hooks - `pre-installation` Executed before the Nextcloud is installed/initiated - `post-installation` Executed after the Nextcloud is installed/initiated - `pre-upgrade` Executed before the Nextcloud is upgraded - `post-upgrade` Executed after the Nextcloud is upgraded - `before-starting` Executed before the Nextcloud starts To use the hooks triggered by the `entrypoint` script, either - Added your script(s) to the individual of the hook folder(s), which are located at the path `/docker-entrypoint-hooks.d` in the container - Use volume(s) if you want to use script from the host system inside the container, see example. Note: Only the script(s) located in a hook folder (not sub-folders), ending with `.sh` and marked as executable, will be executed. Example: Mount using volumes ``` ... app: image: nextcloud:stable volumes: - ./app-hooks/pre-installation:/docker-entrypoint-hooks.d/pre-installation - ./app-hooks/post-installation:/docker-entrypoint-hooks.d/post-installation - ./app-hooks/pre-upgrade:/docker-entrypoint-hooks.d/pre-upgrade - ./app-hooks/post-upgrade:/docker-entrypoint-hooks.d/post-upgrade - ./app-hooks/before-starting:/docker-entrypoint-hooks.d/before-starting ... ``` #### Using the apache image behind a reverse proxy and auto configure server host and protocol The apache image will replace the remote addr (IP address visible to Nextcloud) with the IP address from `X-Real-IP` if the request is coming from a proxy in `10.0.0.0/8`, `172.16.0.0/12` or `192.168.0.0/16` by default. If you want Nextcloud to pick up the server host (`HTTP_X_FORWARDED_HOST`), protocol (`HTTP_X_FORWARDED_PROTO`) and client IP (`HTTP_X_FORWARDED_FOR`) from a trusted proxy, then disable rewrite IP and add the reverse proxy's IP address to `TRUSTED_PROXIES`. - `APACHE_DISABLE_REWRITE_IP` (not set by default): Set to 1 to disable rewrite IP. - `TRUSTED_PROXIES` (empty by default): A space-separated list of trusted proxies. CIDR notation is supported for IPv4. If the `TRUSTED_PROXIES` approach does not work for you, try using fixed values for overwrite parameters. - `OVERWRITEHOST` (empty by default): Set the hostname of the proxy. Can also specify a port. - `OVERWRITEPROTOCOL` (empty by default): Set the protocol of the proxy, http or https. - `OVERWRITECLIURL` (empty by default): Set the cli url of the proxy (e.g. [https://mydnsname.example.com⁠](https://mydnsname.example.com/)) - `OVERWRITEWEBROOT` (empty by default): Set the absolute path of the proxy. - `OVERWRITECONDADDR` (empty by default): Regex to overwrite the values dependent on the remote address. Check the [Nexcloud documentation⁠](https://docs.nextcloud.com/server/latest/admin_manual/configuration_server/reverse_proxy_configuration.html) for more details. Keep in mind that once set, removing these environment variables won't remove these values from the configuration file, due to how Nextcloud merges configuration files together. ### Running this image with Docker Compose The easiest way to get a fully featured and functional setup is using a `compose.yaml` file. There are too many different possibilities to setup your system, so here are only some examples of what you have to look for. At first, make sure you have chosen the right base image (fpm or apache) and added features you wanted (see below). In every case, you would want to add a database container and docker volumes to get easy access to your persistent data. When you want to have your server reachable from the internet, adding HTTPS-encryption is mandatory! See below for more information. #### Base version - apache This version will use the apache image and add a mariaDB container. The volumes are set to keep your data persistent. This setup provides no ssl encryption and is intended to run behind a proxy. Make sure to pass in values for `MYSQL_ROOT_PASSWORD` and `MYSQL_PASSWORD` variables before you run this setup. ``` volumes: nextcloud: db: services: db: image: mariadb:10.6 restart: always command: --transaction-isolation=READ-COMMITTED --log-bin=binlog --binlog-format=ROW volumes: - db:/var/lib/mysql environment: - MYSQL_ROOT_PASSWORD= - MYSQL_PASSWORD= - MYSQL_DATABASE=nextcloud - MYSQL_USER=nextcloud app: image: nextcloud restart: always ports: - 8080:80 links: - db volumes: - nextcloud:/var/www/html environment: - MYSQL_PASSWORD= - MYSQL_DATABASE=nextcloud - MYSQL_USER=nextcloud - MYSQL_HOST=db ``` Then run `docker compose up -d`, now you can access Nextcloud at [http://localhost:8080/⁠](http://localhost:8080/) from your host system. #### Base version - FPM When using the FPM image, you need another container that acts as web server on port 80 and proxies the requests to the Nextcloud container. In this example a simple nginx container is combined with the Nextcloud-fpm image and a MariaDB database container. The data is stored in docker volumes. The nginx container also needs access to static files from your Nextcloud installation. It gets access to all the volumes mounted to Nextcloud via the `volumes_from` option. The configuration for nginx is stored in the configuration file `nginx.conf`, that is mounted into the container. An example can be found in the examples section [here⁠](https://github.com/nextcloud/docker/tree/master/.examples). As this setup does not include encryption, it should be run behind a proxy. Make sure to pass in values for `MYSQL_ROOT_PASSWORD` and `MYSQL_PASSWORD` variables before you run this setup. ``` volumes: nextcloud: db: services: db: image: mariadb:10.6 restart: always command: --transaction-isolation=READ-COMMITTED --log-bin=binlog --binlog-format=ROW volumes: - db:/var/lib/mysql environment: - MYSQL_ROOT_PASSWORD= - MYSQL_PASSWORD= - MYSQL_DATABASE=nextcloud - MYSQL_USER=nextcloud ... Note: the description for this image is longer than the Hub length limit of 25000, so has been trimmed. The full description can be found at [https://github.com/docker-library/docs/tree/master/nextcloud/README.md](https://github.com/docker-library/docs/tree/master/nextcloud/README.md). See also [docker/hub-feedback#238](https://github.com/docker/hub-feedback/issues/238) and [docker/roadmap#475](https://github.com/docker/roadmap/issues/475). ```
Shard	70 (laksa)
Root Hash	8914333203171518870
Unparsed URL	com,docker!hub,/_/nextcloud/ s443