spantaleev / matrix-docker-ansible-deploy

🐳 Matrix (An open network for secure, decentralized communication) server setup using Ansible and Docker
GNU Affero General Public License v3.0
4.89k stars 1.04k forks source link

mx-puppet-slack pre-built image fails to start (again) #1829

Closed aine-etke closed 2 years ago

aine-etke commented 2 years ago

Describe the bug mx-puppet-slack pre-built image fails to start (again) even after the #1825

To Reproduce

Just run the -t setup-all with #1825 changes

Expected behavior It works

Logs

May 16 08:39:53 matrix systemd[1]: Starting Matrix Mx Puppet Slack bridge...
May 16 08:39:58 matrix systemd[1]: Started Matrix Mx Puppet Slack bridge.
May 16 08:40:00 matrix matrix-mx-puppet-slack[1684921]: node:internal/modules/cjs/loader:1151
May 16 08:40:00 matrix matrix-mx-puppet-slack[1684921]:   return process.dlopen(module, path.toNamespacedPath(filename));
May 16 08:40:00 matrix matrix-mx-puppet-slack[1684921]:                  ^
May 16 08:40:00 matrix matrix-mx-puppet-slack[1684921]: Error: Error relocating /opt/mx-puppet-slack/node_modules/canvas/build/Release/canvas.node: pango_fc_font_map_set_default_substitute: symbol not found
May 16 08:40:00 matrix matrix-mx-puppet-slack[1684921]:     at Object.Module._extensions..node (node:internal/modules/cjs/loader:1151:18)
May 16 08:40:00 matrix matrix-mx-puppet-slack[1684921]:     at Module.load (node:internal/modules/cjs/loader:972:32)
May 16 08:40:00 matrix matrix-mx-puppet-slack[1684921]:     at Function.Module._load (node:internal/modules/cjs/loader:813:14)
May 16 08:40:00 matrix matrix-mx-puppet-slack[1684921]:     at Module.require (node:internal/modules/cjs/loader:996:19)
May 16 08:40:00 matrix matrix-mx-puppet-slack[1684921]:     at require (node:internal/modules/cjs/helpers:92:18)
May 16 08:40:00 matrix matrix-mx-puppet-slack[1684921]:     at Object.<anonymous> (/opt/mx-puppet-slack/node_modules/canvas/lib/bindings.js:3:18)
May 16 08:40:00 matrix matrix-mx-puppet-slack[1684921]:     at Module._compile (node:internal/modules/cjs/loader:1092:14)
May 16 08:40:00 matrix matrix-mx-puppet-slack[1684921]:     at Object.Module._extensions..js (node:internal/modules/cjs/loader:1121:10)
May 16 08:40:00 matrix matrix-mx-puppet-slack[1684921]:     at Module.load (node:internal/modules/cjs/loader:972:32)
May 16 08:40:00 matrix matrix-mx-puppet-slack[1684921]:     at Function.Module._load (node:internal/modules/cjs/loader:813:14) {
May 16 08:40:00 matrix matrix-mx-puppet-slack[1684921]:   code: 'ERR_DLOPEN_FAILED'
May 16 08:40:00 matrix matrix-mx-puppet-slack[1684921]: }
May 16 08:40:00 matrix systemd[1]: matrix-mx-puppet-slack.service: Main process exited, code=exited, status=1/FAILURE
aine-etke commented 2 years ago

@dsonck92 could you check it, please?

dsonck92 commented 2 years ago

It seems like the pipeline used a different node while building than the dockerfile from used. I did some changes to that to fix this, so I'm rerunning the pipeline so v0.1.1 will be retagged with a working version.

spantaleev commented 2 years ago

It might be safer to retag as v0.1.1-2 or v0.1.2 or something, so that people who already pulled via the playbook will get a new one when we bump our version. We (and Docker in general) don't force-pull tags, as we don't expect them to have changed (unless it's :latest).

dsonck92 commented 2 years ago

In general I do agree with that stance, except that in this case the image was not functional at all due to misconfigured external ci config. There's actually no change in the code at all as all bridges build from the same instructions. But I can create a new tag, which would be exactly the same as v0.1.1.

dsonck92 commented 2 years ago

Actually, scratch that, the pipeline failed anyways, so I'll be trying to build v0.1.2

dsonck92 commented 2 years ago

Version v0.1.2 is out now. Again, I don't use it myself, but I think it should work considering the branch version mentioned earlier was tested by someone, and this only builds everything on node 17, and ensures all stages do that.

spantaleev commented 2 years ago

I've upgraded us to v0.1.2. Hopefully it works!

dsonck92 commented 2 years ago

Alright! Well, please let me know, for me it's also better if I can safely say v0.1.2 works (which should have been v0.1.0)

aine-etke commented 2 years ago

It works, thank you!