The php module imagick is not enabled nextcloud
Hi Community, must be install php-imagick for Nextcloud 24.0.1, but it is not aviable on Nextcloud Instans apt install php-imagick --> not work has someone a solution ? Best regards, B U S T E R
Is your problem is what is described here: I run a the plain docker version of Nextcloud and just opened a shell in the Nextcloud app and pasted in the commands there: # apt -y update
Is your problem is what is described here: I run a the plain docker version of Nextcloud and just opened a shell in the Nextcloud app and pasted in the commands there: # apt -y update thanks
for try to help, this i have always installed, issue is more --> "php-imagick in this instance has no SVG support"
thanks for try to help, this i have always installed, issue is more --> "php-imagick in this instance has no SVG support" Did you read the link I posted? If you did, please rephrase the above so I can understand your problem.
Did you read the link I posted? If you did, please rephrase the above so I can understand your problem. I had overlooked your link..
Yes, this is the Truenas Scale forum, so I assumed as much. You should not do what is described in the link. You should do what is described in my first post. Open a shell in the App/container and execute these commands: # apt -y update If the container is upgraded/reloaded you will need to redo this.
Yes, this is the Truenas Scale forum, so I assumed as much. You should not do what is described in the link. You should do what is described in my first post. Open a shell in the App/container and execute these commands: # apt -y update If the container is upgraded/reloaded you will need to redo this. this command i do it yes sure in App/container but after refresh site issue persist instantly
i have found a Note in Nextcloud.com FAQ --> https://docs.nextcloud.com/server/1...ion.html?highlight=svg#previews-configuration Note it is Disabled sites from Nextcloud himself ore what they will tell us ?
just going to point out that running apt with in a container anyways is a little silly since next time the up stream container is updated its just going to wipe it out. any situation where you need to add extra options to a container you should do one of 2 things A Create build maintain and host your own container with the needed options installed
On our App the following related packages are already installed:
just going to point out that running apt with in a container anyways is a little silly since next time the up stream container is updated its just going to wipe it out. any situation where you need to add extra options to a container you should do one of 2 things A
Create build maintain and host your own container with the needed options installed Given that this is a permanent problem, your suggestions make sense.
So if the official Nextcloud image is indeed fixed soon, I believe re-running apt once or twice is much preferred to creating alternate containers or VMs.
On our App the following related packages are already installed: Yes. If I had been starting from scratch, using Truecharts would have been the way to go. I did upgrade to Scale from
Core and had an existing Nextcloud installation, using Mariadb. So I figured using the standard Nextcloud docker image was simpler, just reusing my data-directory and database.
Given that this is a permanent problem, your suggestions make sense. So if the official Nextcloud image is indeed fixed soon, I believe re-running apt once or twice is much preferred to creating alternate
containers or VMs. This is incorrect information. We've had to apply this fix for months by now and there seems to be no activity from the people at Nextcloud on this front at all.
This is incorrect information. We've had to apply this fix for months by now and there seems to be no activity from the people at Nextcloud on this front at all. By
incorrect I assume you mean that it won't be fixed soon? I did some more research and see that this has been discussed rather actively for a while: There are some security concerns with this library, but I see that there now seems to be consensus that it should be included. One can hope. I'm perfectly happy to live with the current situation. I have no adverse effects of the missing library, apart from the warning. And if that bothers me I just reinstall with apt in the
container.
This is incorrect information. We've had to apply this fix for months by now and there seems to be no activity from the people at Nextcloud on this front at all. how
can you explain why the error message happens to me? PS: something else where is the php.ini file stored? Last edited: Jun 28, 2022
how can you explain why the error message happens to me? PS: something else where is the php.ini file stored? If you
have any feedback about things we build, please contact us directly.
how can you explain why the error message happens to me? PS: something else where is the php.ini file stored? did
you ever find a resolution to finding the php.ini file?
did you ever find a resolution to finding the php.ini file? As explained by our staff quite a few time to you this week: We do *not* block access to shell and we do *not* set the php-fpm settings. Those are the upstream settings they configured to be used. It would be nice if you could stop spreading information which was already explained to be untrue multiple times, like your repeated comments about us locking people out of the shell. That's simply completely untrue. The containers we do build ourselves (which is just a handfull), have full shell access. The rest are simply mirrored. *edit*
Run TrueNAS CORE and FreeBSD jails if you want persistent transparent containers. No intention to snub SCALE, TrueCharts or Docker in general, but there are always alternatives and people with different approaches to systems. |