3/30/2023 0 Comments Bitnami owncloud freenas data 770![]() Sometimes it's hard for us to continue improving our charts as new features of Kubernetes appear without including backwards incompatibilities. Our apologizes if the migration process wasn't smooth. As you can see, from now on, the chart forces you to indicate the credentials (so this error won't appear again). Many of the changes included in the major version 10.0.0 are intended to improve the stability of the chart so, hopefully, you shouldn't face many issues in the future. Hi to find out you find no issues with the new chart. Upgrade the chart setting -set containerSecurit圜nAsUser=0,podSecurit圜ontext.fsGroup=0 (this will basically revert the changes in the ownCloud image so it's run as a root container).(perform this step only if you have important data you don't want to lose) Restore the backup in the new chart.Install the chart using latest version.Uninstall the helm chart and remove the associated PVCs. ![]() (perform this step only if you have important data you don't want to lose) Make a backup of your ownCloud database and data (see ).The most important change is related to transforming ownCloud in a non-root container by default, that's also documented in the image repo, see:Īs a consequence of all these changes, to migrate from 9.x to 10.x, you mainly have two alternatives: Hi are big changes included in version 10.x respect to prior versions. dev/disk/by-id/scsi-0Linode_Volume_pvcc664b4ca65794909 on /bitnami/owncloud type ext4 (rw,relatime) $ kubectl exec -n owncloud owncloud-76c86b9465-zhnlc - mount | grep own $ kubectl exec -n owncloud owncloud-76c86b9465-zhnlc - ls -la /bitnami/owncloud/ĭrwxrwsr-x 3 root 1001 4096 Feb 2 10:05. Ls: cannot access '/bitnami/owncloud/config': No such file or directory $ kubectl exec -n owncloud owncloud-76c86b9465-zhnlc - ls -la /bitnami/owncloud/config Owncloud-5f5fb5c447-sxhd5 0/1 ContainerCreating 0 3m7s I think I might be better off starting afresh. Guessing this file should exist on the persistent storage, right? Which makes me wonder about the persistent storage my cloud provider (linode) provides. Realpath: /bitnami/owncloud/config/config.php: No such file or directory Owncloud 10:05:53.36 INFO => Restoring persisted ownCloud installation Owncloud 10:05:53.26 INFO => Validating settings in MYSQL_CLIENT_* env vars Owncloud 10:05:53.25 INFO => Configuring PHP options Owncloud 10:05:53.23 INFO => Configuring the HTTPS port Owncloud 10:05:53.22 INFO => Configuring the HTTP port Owncloud 10:05:53.21 INFO => ** Starting ownCloud setup ** Owncloud 10:05:53.20 Submit issues and feature requests at Owncloud 10:05:53.20 Subscribe to project updates by watching Owncloud 10:05:53.20 Welcome to the Bitnami owncloud container Kubectl logs -n owncloud owncloud-5f5fb5c447-rt6wd Mariadb should start correctly, or at least log an error that I can use to diagnose problem. (Any restart of the mariadb I think might actually cause this) Mariadb 00:11:51.56 INFO => Stopping mariadb Mariadb 00:11:49.53 INFO => Starting mariadb in background Mariadb 00:11:49.53 INFO => Running mysql_upgrade Mariadb 00:11:49.51 INFO => Using persisted data Configurations based on environment variables will not be applied for this file. Mariadb 00:11:49.50 WARN => The mariadb configuration file '/opt/bitnami/mariadb/conf/my.cnf' is not writable. Mariadb 00:11:49.49 INFO => Initializing mariadb database Mariadb 00:11:49.49 INFO => Validating settings in MYSQL_*/MARIADB_* env vars Mariadb 00:11:49.47 INFO => ** Starting MariaDB setup ** Mariadb 00:11:49.47 Submit issues and feature requests at Mariadb 00:11:49.47 Subscribe to project updates by watching Mariadb 00:11:49.47 Welcome to the Bitnami mariadb container ![]() $ kubectl logs -n owncloud owncloud-mariadb-0
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |