Open catmurdock opened 1 month ago
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.
You've potentially got a broken third party app installed. Also side note those ENV's for the sql details don't work in our container.
Maybe the theme is broken as wel
2024/10/18 22:14:48 [error] 438#438: *1 open() "/app/www/public/apps/theming/img/background/jenna-kim-the-globe.webp" failed (13: Permission denied), client: xx server: _, request: "GET /apps/theming/img/background/jenna-kim-the-globe.webp HTTP/1.1", host: "
Installing dependencies from lock file (including require-dev) Verifying lock file contents can be installed on current platform. Package operations: 1 install, 0 updates, 0 removals
[ $COMPOSER_DEV_MODE -eq 0 ] || composer bin all install [bamarni-bin] Could not find any bin namespace. composer dump-autoload --no-dev Generating optimized autoload files Class FeedBackHandler located in ./core/ajax/update.php does not comply with psr-4 autoloading standard (rule: OC\Core\ => ./core). Skipping. Generated optimized autoload files containing 2001 classes
:/app/www/public#occ An unhandled exception has been thrown: Error: Failed opening required '/app/www/public/apps/files/composer/autoload.php' (include_path='/app/www/public/3rdparty/pear/archive_tar:/app/www/public/3rdparty/pear/console_getopt:/app/www/public/3rdparty/pear/pear-core-minimal/src:/app/www/public/3rdparty/pear/pear_exception:/app/www/public/apps') in /app/www/public/lib/private/legacy/OC_App.php:118 Stack trace:
/app/www/public#composer update --no-scripts Loading composer repositories with package information Updating dependencies Nothing to modify in lock file Installing dependencies from lock file (including require-dev) Nothing to install, update or remove Generating optimized autoload files
You need to check nextcloud for any issues with the apps/themes you're using. This isn't a container issue.
I had encounter same error, not able to downgrade with previous version. please help.. 😢. Something is wrong with latest container...
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.
Is there an existing issue for this?
Current Behavior
after updating the latest image it failed to start. I have done some basic troublshooting but it didnt work
Expected Behavior
this happen after updating the latest docker image
Steps To Reproduce
I have redeploy the image, but still the same, downgrading is not supported
Environment
CPU architecture
x86-64
Docker creation
Container logs