angristan / docker-pleroma

Docker image for the Pleroma federated social network
https://git.pleroma.social/pleroma/pleroma/
MIT License
348 stars 75 forks source link

Unable to build Pleroma on latest develop commit #35

Open darthdubu opened 2 years ago

darthdubu commented 2 years ago

Pleroma build fails seemingly stating a missing dependency "crypt".

Generated http_signatures app
make: Entering directory '/pleroma/deps/crypt/c_src'
cc -DHAVE_CRYPT_R -O3 -std=c99 -finline-functions -Wall -Wmissing-prototypes -pedantic -fwrapv -D_FORTIFY_SOURCE=2 -fstack-protector-strong -Wformat -Werror=format-security -fno-strict-aliasing -Wconversion -Wshadow -Wpointer-arith -Wcast-qual -fPIC -I /usr/local/lib/erlang/erts-11.2.2.6/include/ -c -o /pleroma/deps/crypt/c_src/explicit_bzero.o /pleroma/deps/crypt/c_src/explicit_bzero.c
/pleroma/deps/crypt/c_src/explicit_bzero.c:35:54: error: 'bzero' undeclared here (not in a function)
   35 | static void (* volatile ssh_bzero)(void *, size_t) = bzero;
      |                                                      ^~~~~
make: *** [Makefile:61: /pleroma/deps/crypt/c_src/explicit_bzero.o] Error 1
make: Leaving directory '/pleroma/deps/crypt/c_src'
===> Hook for compile failed!

==> pleroma
** (Mix) Could not compile dependency :crypt, "/pleroma/.mix/rebar3 bare compile --paths="/pleroma/_build/prod/lib/*/ebin"" command failed. You can recompile this dependency with "mix deps.compile crypt", update it with "mix deps.update crypt" or clean it with "mix deps.clean crypt"
The command '/bin/sh -c mix local.rebar --force     && mix local.hex --force     && mix deps.get     && mix compile' returned a non-zero code: 1
zhoreeq commented 2 years ago

Same problem

sabotagebeats commented 2 years ago

I have the same issue on raspberry pi 4 ubuntu 20.04 LTS 64 bit

Radtoo commented 2 years ago

Same here. I believe it is this upstream issue.

mknet commented 2 years ago

Has someone solved the issue yet?

reppard commented 2 years ago

hey folks. i was able to successfully build by changing the image tag to elixir:1.9-alpine. thats what the upstream is building from currently.

FROM elixir:1.9-alpine
angristan commented 2 years ago

Should we update the Dockerfile to 1.9?

reppard commented 2 years ago

Should we update the Dockerfile to 1.9?

potentially? while i was able to build, running was a different story.

The upstream entrypoint was throwing errors when trying to bring up the web service:

pleroma_ctl and pleroma are absent from PATH

echo "-- Running migrations..."
$HOME/bin/pleroma_ctl migrate

echo "-- Starting!"
exec $HOME/bin/pleroma start