![](http://content.invisioncic.com/u329766/set_resources_34/84c1e40ea0e759e3f1505eb1788ddf3c_pattern.png)
blaine07
-
Posts
754 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by blaine07
-
-
Upgrade fine for me. I however don’t think I’ve ever seen so many “BZimage Checksum” errors on a upgrade cycle. Happened to me on my T610 when going into the RCs and had to turn off the setting in Dells that causes issue.
BZimage thing is concerning.
-
Why yes!
I was just trying to fix this, and I think I found the answer. The container is trying to use NUMA for resource allocation with the host, but is being gated by the default security profile.
To fix: Edit the container, enable advanced view, and add:
--cap-add=sys_nice--cap-add=sys_nice
to Extra Parameters. Apply and profit.
The seccomp workaround is messy, it disables all the normal security for the container. The call to mbind is now already gated by CAP_SYS_NICE, but if you want to use it you'll have to tune the security profile for the container.
Hope it helps!
-P
Worked. Thank you mate! -
Why yes!
I was just trying to fix this, and I think I found the answer. The container is trying to use NUMA for resource allocation with the host, but is being gated by the default security profile.
To fix: Edit the container, enable advanced view, and add:
--cap-add=sys_nice--cap-add=sys_nice
to Extra Parameters. Apply and profit.
The seccomp workaround is messy, it disables all the normal security for the container. The call to mbind is now already gated by CAP_SYS_NICE, but if you want to use it you'll have to tune the security profile for the container.
Hope it helps!
-P
Will try this in a bit. I don’t think error actually hurts anything… other than me because I know it’s there LOL
Thank you! -
I searched this thread first and no dice. In MySQL container trying to find a way to suppress "mbind: Operation not permitted."
It appears it's possible to suppress the message? https://docs.docker.com/engine/security/seccomp/#run-without-the-default-seccomp-profile
Anyone have any insight/help?
-
Either/any of yall using pfsense or something by chance?
EDIT: with PfSense I had a bunch of issues after switching and my fix was
Maybe something like this is breaking your setup?
-
I updated to v24, no problems yet!
Noticed anything new, shiny and cool? Seems a 24 changelog is MIA lol? -
So… is it safe to move to 24 yet? [emoji848]
-
22 minutes ago, A75G said:
okay change it to "ALL" without quotation. i have updated the template
So I will run “backup-now ALL”?
How do I update template on my end?
-
2 minutes ago, A75G said:
Try adding DB_NAME variable with each databases you have for example: nextcloud,authelia,freshrss,mysql
Is their not a way to define "all"? (I don't even know names of all the DBs on the MariaDB server it's backing up LOL). I know before version 3.3.2 I was on V2.12.0. On 2.12.0 "backup-now" just grabbed them all. Not sure why that functionality would be depreciated?
(thank you, for the reply!)
-
-
I wish I understood exactly what was going on here and if adding these ARGS is going to cause more issues later.
-
2
-
-
-
This is a basic function of docker and is valid for all containers.
Are you aware of any guides or tutorials to do this correctly with Unraid?
All the thanks, as usual :-) -
I realize that after container has been created this process may vary slightly but is there a way to connect this container to multiple networks?
There’s a different version of NPM floating around and it supports such. Does this container support it too? If so, how does one set it up after container has already been created? Does the —net flag still need passed through?
For reference, this is other container, but wondering if this is applicable to this container too: -
2 minutes ago, Tolete said:
the NPM proxy config on post/using came from NPM github you can refer to post for reference.
https://github.com/NginxProxyManager/nginx-proxy-manager/issues/70
Hey mate, all the thanks through making these changes! I truly appreciate it! 🙂
-
3 hours ago, Tolete said:
post updated. new config
Is this new config supposed to make /admin not available outside LAN? I can't find any difference between what you initially posted for "Admin" and the new admin config?
Also, on bottom of Edit Proxy Host on NPM it says:
Please note, that any add_header or set_header directives added here will not be used by nginx. You will have to add a custom location '/' and add the header in the custom config there.
The config you have shared includes proxy set header directives? It says they wont work?
-
Yeah I don’t see the _ anywhere defined. I’m super confused by all this lol -
I just had a breakthrough, don't know if it's luck or the actual solution, but for me,
Key: alias_group1
Value: https://my\\.nextcloud\\.domain:443
worked, finally.
Apparently the _ between alias and group1 is quite important. Don't know how others have gotten it to work, but that's what did it for me.
What version Collabora you using? -
3 minutes ago, Tolete said:
see updated post.
See my post above about admin panel.
Does this:
# Admin Console websocket
location ^~ /lool/adminws {
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
proxy_http_version 1.1;
proxy_pass $forward_scheme://$server:$port;
proxy_set_header Host $http_host;
proxy_read_timeout 36000s;
}need to change because admin URL changed?
EDIT: also, using above, is there a way to make the ADMIN page only accessible internally and not at all outside LAN?
-
Oh, admin portal can now be found at: https://[IP]:[PORT:9980]/browser/dist/admin/admin.html
FOR REFENCE THE OLD ADMIN was: https://[IP]:[PORT:9980]/loleaflet/dist/admin/admin.html
-
25 minutes ago, Tolete said:
what do you have for your collabora repository?
I figured it out; had to enter alias like "https:/sub.domain.net:443"
Any idea on where ADMIN page lies now?
My repository: collabora/code:21.11.3.6.1
-
Just now, Tolete said:
i have updated pic/post
documentation says/pic show 'aliasgroup1' the '|' in pic is just the cursor.
It didn't work for me with just one "l" but does with two? I dont understand lol
-
Also, does anyone know where admin resides now? Can't seem to find it?
It used to be at "https://[IP]:[PORT:9980]/loleaflet/dist/admin/admin.html"
Now that 404s?
-
3 hours ago, Tolete said:took a second look at this got it up and running.
steps i took--
reinstall/enable 'Nextcloud Office' (5.0.3) app.
Collabora (latest)-
edit container and remove the 'Domain' Variable.
add new Variable
save.
in NginxProxyManager-
specify https protocol and the server host/ip and port 9980. Also enable Websockets Support.
On the SSL tab select a new certificate, enable HTTP/2.
On the Advanced tab, enter:# static fileslocation ^~ /loleaflet { proxy_pass $forward_scheme://$server:$port; proxy_set_header Host $http_host;}# WOPI discovery URLlocation ^~ /hosting/discovery { proxy_pass $forward_scheme://$server:$port; proxy_set_header Host $http_host;}# main websocketlocation ~ ^/lool/(.*)/ws$ { proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade"; proxy_http_version 1.1; proxy_pass $forward_scheme://$server:$port; proxy_set_header Host $http_host; proxy_read_timeout 36000s;}# download, presentation and image uploadlocation ~ ^/lool { proxy_pass $forward_scheme://$server:$port; proxy_set_header Host $http_host;}# Admin Console websocketlocation ^~ /lool/adminws { proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade"; proxy_http_version 1.1; proxy_pass $forward_scheme://$server:$port; proxy_set_header Host $http_host; proxy_read_timeout 36000s;}
save and test.
Your pic shows “alliasgroup1”
Should it be as shown or “aliasgroup1” with ONE “l”?edit: weird it only does work with TWO “l”. I don’t understand; I don’t see it expressed as anywhere with “alliasgroup” so don’t understand why that works. 🤦🏼♂️
Unraid OS version 6.10.0 available
in Announcements
Posted
You might check this out.
https://forums.unraid.net/topic/119502-bzimage-checksum-error/