Collaborative editing does not work sometimes about docker-atlassian-confluence HOT 8 CLOSED

Same here. Added another glibc compat alternative and its working now.

FROM cptactionhank/atlassian-confluence:6.7.1

USER root

# workaround for running native lib /tmp/snappy-1.1.0.1-327f818c-0e3b-40a0-85f0-2c773e1e7fac-libsnappyjava.so
# see https://github.com/xerial/snappy-java
RUN set -ex \
    && wget -q -O /etc/apk/keys/sgerrand.rsa.pub https://raw.githubusercontent.com/sgerrand/alpine-pkg-glibc/master/sgerrand.rsa.pub \
    && wget https://github.com/sgerrand/alpine-pkg-glibc/releases/download/2.27-r0/glibc-2.27-r0.apk \
    && apk add --no-cache glibc-2.27-r0.apk \
    && rm glibc-2.27-r0.apk

USER daemon

from docker-atlassian-confluence.

Thank you very very much, @inash !
Your comment absoulutely saved my day.
I first thought that removing my old workaround would be enough, after all, the solution to this problem should be now incorporated into the regular docker image, right?

Well no, the problem was back, and I assume affects every single user of the image (or at least everybody with an application link to jira)! (certain confluence sites can not be edited, links to jira do not render in page).

running "apk add gcompat" in the container and then restarting it fixed both problems.

Again, I would suggest adding that to the docker image so that such obscure fixes are not needed!(though admittedly installing a package through the package management system is at least cleaner than hardcoding using wget to fetch a specific version of glibc ...)

from docker-atlassian-confluence.

Can confirm, fixed a strange problem that

/synchrony/v1/data/Synchrony-...

routes always responded with 404 code and "missing token" body. Since adding this to the image, those two errors are gone if the editor is loaded.

from docker-atlassian-confluence.

Thank you!
We had the same problem: Certain sites could not be edited. Interestingly even though collaborative editing was disabled!
Additionally jira links would not display correctly.
Anyway, we had the same error messages, so I tried the fix, and after a restart both issues have now been resolved.

In light of the fact that cptactionhank offers both confluence and jira docker instances, it would be great if that fix could be integrated into the build!

from docker-atlassian-confluence.

Should be fixed now, branches based on Alpine are updated. Please pull the new version and create your containers again.

from docker-atlassian-confluence.

Hi, I had to additionally add gcompat package to make it work with the recent 6.14.1 image.

from docker-atlassian-confluence.

Nice! Thank you! This also helped in my case.

I've just pushed my update to my repo https://github.com/dsteinkopf/confluence-dup and docker hub https://cloud.docker.com/repository/docker/dsteinkopf/confluence-dup - if anyone might find this helpful here.

from docker-atlassian-confluence.

gcompat seems to have been added to the latest image in #79

from docker-atlassian-confluence.