-
Notifications
You must be signed in to change notification settings - Fork 272
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Environment not properly prepared #220
Comments
Hoi! I haven't actually seen this before, but others can chime in if they have. Could you test again with the current nextcloud helm chart version and values.yaml? It looks like you're using It also looks like you're using If you're still having the issue, I might ask that you enable a more verbose logging level with the following: nextcloud:
configs:
# Log Levels: 0=DEBUG, 1=INFO, 2=WARN, 3=ERROR, 4=FATAL
logging.config.php: |-
<?php
$CONFIG = array (
'log_type' => 'file',
'logfile' => 'nextcloud.log',
'loglevel' => 2,
'logdateformat' => 'F d, Y H:i:s'
); Logging is explained a bit further here But you should be able to check the log from within the pod, and paste it back here. Let me know if you have further questions! :) |
Can you also try on k3s or kind? |
Closing, as this Issue hasn't had activity in over a year, and I can't seem to reproduce it. If you, or anyone else in the community, is still having issues on the latest version of the helm chart (and Kubernetes), please feel free to open a new issue and we're happy to help you out. :) Kind regards! |
I seem to be running into this issue as well. Chart version: 6.1.0 Non-default values: nextcloud:
host: "nextcloud.my.domain"
trustedDomains:
- "nextcloud.my.domain"
- "nextcloud.nextcloud.svc.cluster.local"
configs:
logging.config.php: |-
<?php
$CONFIG = array (
'log_type' => 'file',
'logfile' => 'nextcloud.log',
'loglevel' => 0,
'logdateformat' => 'F d, Y H:i:s'
);
custom-overwrite.config.php: |-
<?php
$CONFIG = array (
'overwrite.cli.url' => 'https://nextcloud.nextcloud.svc.cluster.local',
'overwriteprotocol' => 'https',
);
proxy.config.php: |-
<?php
$CONFIG = array (
'trusted_proxies' => array(
0 => '127.0.0.1',
1 => '10.0.0.0/8',
),
'forwarded_for_headers' => array('HTTP_X_FORWARDED_FOR'),
);
securityContext:
runAsUser: 33
runAsGroup: 33
runAsNonRoot: true
readOnlyRootFilesystem: false
persistence:
enabled: true Pod logs:
A tail of nextcloud logs
Shelling into pod and trying to run this command: php occ config:system:get trusted_domains
Your data directory is readable by other users.
Please change the permissions to 0770 so that the directory cannot be listed by other users.
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(99): 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...') Also found these errors higher up in the nextcloud logs:
I need to be able to run this container as nonroot. Any ideas what is going on here or what I could look into? |
Adding this allowed me to get the pod to startup correctly:
But the underlying issue seems to be related to: #335 |
I'm trying to deploy Nextcloud using Helm. First I tried it on my local machine (MacOS Big Sur) using Minikube (Kubernetes 1.21) and it was up and running in 5 minutes.. Unfortunately it will not succeed at work. I'm using there CentOS7 to eventually deploy Nextcloud on a Kubernetes cluster 1.21.
The error I retrieve:
Environment not properly prepared in /var/www/html/lib/private/Console/Application.php:162
. See image below:My values.yml file looks like this:
Has this something to do with some config.php files I need to add?
The text was updated successfully, but these errors were encountered: