You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am using minIO to be my primary storage.
I use docker compose to setup my nextcloud server.
First Time
I reset my nextcloud's db and minIO bucket to empty
I also keep config file to empty (I didn't create it)
When I docker compose up to start my nextcloud
Everything are work fine
The init media and file also upload to my minio server
When I use docker compose down to close nextcloud server
Second Time
I use docker compose up start the nextcloud server again
This time we keep the origin config file
The bad thing is happen
The nextcloud show me data folder is invalid and please check .ocdata is exist
I try to figure out it, so I use docker logs to show the log like following
docker logs nextcloud
Initializing nextcloud 29.0.4.1 ...
New nextcloud instance
Installing with MySQL database
=> Searching for scripts (*.sh) to run, located in the folder: /docker-entrypoint-hooks.d/pre-installation
Starting nextcloud installation
Your data directory is invalid.
Ensure there is a file called ".ocdata" in the root of the data directory.
An unhandled exception has been thrown:
Exception: Environment not properly prepared. in /var/www/html/lib/private/Console/Application.php:167
Stack trace:
#0 /var/www/html/console.php(101): OC\Console\Application->loadCommands(Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput)) #1 /var/www/html/occ(11): require_once('/var/www/html/c...') #2 {main}Retrying install...
Your data directory is invalid.
Ensure there is a file called ".ocdata" in the root of the data directory.
I think this is a bug
It look like if you use minIO to be primary storage
you must lost the .ocdata, but I think this is incorrect
You need to also persist the data directory even if you use object storage as primary storage. There (could be / are) still some (small) files written to that directory for compatibility reasons, see also documentation:
By default, files are stored in nextcloud/data or another directory configured in the config.php of your Nextcloud instance. This data directory might still be used for compatibility reasons)
Bug description
I am using minIO to be my primary storage.
I use docker compose to setup my nextcloud server.
First Time
I reset my nextcloud's db and minIO bucket to empty
I also keep config file to empty (I didn't create it)
When I docker compose up to start my nextcloud
Everything are work fine
The init media and file also upload to my minio server
When I use docker compose down to close nextcloud server
Second Time
I use docker compose up start the nextcloud server again
This time we keep the origin config file
The bad thing is happen
The nextcloud show me data folder is invalid and please check .ocdata is exist
I try to figure out it, so I use docker logs to show the log like following
docker logs nextcloud
Initializing nextcloud 29.0.4.1 ...
New nextcloud instance
Installing with MySQL database
=> Searching for scripts (*.sh) to run, located in the folder: /docker-entrypoint-hooks.d/pre-installation
Starting nextcloud installation
Your data directory is invalid.
Ensure there is a file called ".ocdata" in the root of the data directory.
An unhandled exception has been thrown:
Exception: Environment not properly prepared. in /var/www/html/lib/private/Console/Application.php:167
Stack trace:
#0 /var/www/html/console.php(101): OC\Console\Application->loadCommands(Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))
#1 /var/www/html/occ(11): require_once('/var/www/html/c...')
#2 {main}Retrying install...
Your data directory is invalid.
Ensure there is a file called ".ocdata" in the root of the data directory.
I think this is a bug
It look like if you use minIO to be primary storage
you must lost the .ocdata, but I think this is incorrect
This is my env info
Config
REVERSE_PROXY_NETWORK=micro-service
DOMAIN=example.com
Resource limits
CPUS=4
MEMORY_BYTES=4g # 4GB in bytes
Nextcloud Docker settings
NEXTCLOUD_IMAGE=nextcloud:29.0.4-apache
NEXTCLOUD_CONTAINER_NAME=nextcloud
Database settings (MySQL or MariaDB)
DB_HOST=192.168.2.249
DB_NAME=nextcloud_minio
DB_USER=nextcloud
DB_PASSWORD=passwd
Nextcloud admin user
NEXTCLOUD_ADMIN_USER=nextcloud
NEXTCLOUD_ADMIN_PASSWORD=passwd
MinIO (S3-compatible) settings
OBJECTSTORE_S3_HOST=minio-cluster.localdomain
OBJECTSTORE_S3_PORT=80
OBJECTSTORE_S3_REGION=eu-west-1
OBJECTSTORE_S3_BUCKET=nextcloud-test
OBJECTSTORE_S3_ACCESS_KEY=xxx
OBJECTSTORE_S3_SECRET_KEY=ooo
OBJECTSTORE_S3_USE_SSL=false
OBJECTSTORE_S3_USE_PATH_STYLE=true
Steps to reproduce
Expected behavior
I think the .ocdata shouldn't happen when I use docker compose down & up
Everything like no change
Nextcloud Server version
29
Operating system
Debian/Ubuntu
PHP engine version
None
Web server
Apache (supported)
Database engine version
MySQL
Is this bug present after an update or on a fresh install?
Fresh Nextcloud Server install
Are you using the Nextcloud Server Encryption module?
None
What user-backends are you using?
Configuration report
No response
List of activated Apps
No response
Nextcloud Signing status
No response
Nextcloud Logs
No response
Additional info
No response
The text was updated successfully, but these errors were encountered: