pleroma/pleroma-docker-compose
0
0
Fork 0
Code Issues 2 Pull requests 2 Projects Releases Packages Wiki Activity

not working with pleroma:latest #3

New issue
Open
opened 2023-11-12 14:40:04 +00:00 by gitlab-ghost-3733 · 4 comments
gitlab-ghost-3733 commented 2023-11-12 14:40:04 +00:00
Member
Copy link

How to reproduce

git clone https://git.pleroma.social/pleroma/pleroma-docker-compose.git
cd pleroma-docker-compose
docker compose up -d pleroma-db
sleep 30
docker compose up pleroma

What happened

  • Pleroma fails to start
pleroma     | -- Waiting for database...
pleroma     | pleroma-db:5432 - accepting connections
pleroma     | -- Running migrations...
pleroma     | ERROR! Config provider Pleroma.Config.ReleaseRuntimeProvider failed with:
pleroma     | ** (RuntimeError) Configuration at /etc/pleroma/config.exs has world-permissions, execute the following: chmod o= /etc/pleroma/config.exs
pleroma     |     lib/pleroma/config/release_runtime_provider.ex:27: Pleroma.Config.ReleaseRuntimeProvider.load/2
pleroma     |     (elixir 1.11.4) lib/config/provider.ex:347: anonymous fn/2 in Config.Provider.run_providers/2
pleroma     |     (elixir 1.11.4) lib/enum.ex:2193: Enum."-reduce/3-lists^foldl/2-0-"/3
pleroma     |     (elixir 1.11.4) lib/config/provider.ex:204: Config.Provider.boot_providers/4
pleroma     |     :init.eval_script/2
pleroma     |     :init.do_boot/3
pleroma     | 
pleroma     | 
pleroma     | {"init terminating in do_boot",{#{'__exception__'=>true,'__struct__'=>'Elixir.RuntimeError',message=><<"Configuration 
pleroma     | at /e
pleroma     | tc
pleroma     | /pleroma/config
pleroma     | .exs has w
pleroma     | orld-pe
pleroma     | rmission
pleroma     | s, execute the 
pleroma     | following: ch
pleroma     | mod o= /etc/
pleroma     | pleroma/c
pleroma     | onfig.
pleroma     | exs">>}
pleroma     | ,[{'Elixir.Pleroma.Conf
pleroma     | ig.ReleaseRuntimeProvider',load,2,[{file,"lib/pleroma/config/release_runtime_provider.ex"},{line,27}]},{'Elixir.
pleroma     | Config.Pro
pleroma     | vider',
pleroma     | '-run_p
pleroma     | rovider
pleroma     | s/2-
pleroma     | fun
pleroma     | -0
pleroma     | -',2,[{
pleroma     | file,
pleroma     | "lib
pleroma     | /con
pleroma     | fig/provid
pleroma     | er.ex"}
pleroma     | ,{line,347}]},{'El
pleroma     | ixir.Enum','-reduce/3-l
pleroma     | ists^foldl/2-0
pleroma     | -',3,[{f
pleroma     | ile,"lib/
pleroma     | enum.ex"},{li
pleroma     | ne,2193}]},
pleroma     | {'Elix
pleroma     | ir.Config
pleroma     | .Provid
pleroma     | er',bo
pleroma     | ot_prov
pleroma     | iders,4,[{
pleroma     | file,"
pleroma     | lib/con
pleroma     | fig/provi
pleroma     | der.ex"},
pleroma     | {line,2
pleroma     | 04}]},{in
pleroma     | it,eva
pleroma     | l_script,
pleroma     | 2,[]},
pleroma     | {init,
pleroma     | do_boot,3
pleroma     | ,[]}]}
pleroma     | }
pleroma     | init terminating in do_boot (
pleroma     | {,[{Eli
pleroma     | xir.Ple
pleroma     | roma.Confi
pleroma     | g.Relea
pleroma     | seRunti
pleroma     | meProvi
pleroma     | der,lo
pleroma     | ad,2,[{_},
pleroma     | {_}]},
pleroma     | {Elixir
pleroma     | .Config
pleroma     | .Provider,
pleroma     | -run_provi
pleroma     | ders/2-f
pleroma     | un-0-,2
pleroma     | ,[{_},{
pleroma     | _}]},{Elix
pleroma     | ir.Enum
pleroma     | ,-reduce/
pleroma     | 3-lists
pleroma     | ^foldl/2-0
pleroma     | -,3,[{_
pleroma     | },{_}]},{
pleroma     | Elixir.
pleroma     | Config.
pleroma     | Provide
pleroma     | r,boot_
pleroma     | provide
pleroma     | rs,4,[{_},
pleroma     | {_}]},{in
pleroma     | it,eval_s
pleroma     | cript,2,[]
pleroma     | },{init
pleroma     | ,do_boo
pleroma     | t,3,[]}
pleroma     | ]})
pleroma     | 
pleroma     | Crash dump is being written to:
pleroma     |  erl_crash.dump..
pleroma     | .
pleroma exited with code 0
  • I can not take a quick look if Pleroma is something for me or not.

What should happen

  • It should just work so that I can play around with Pleroma on localhost to see if it is something for me or not.
# How to reproduce ``` git clone https://git.pleroma.social/pleroma/pleroma-docker-compose.git cd pleroma-docker-compose docker compose up -d pleroma-db sleep 30 docker compose up pleroma ``` # What happened * Pleroma fails to start ``` pleroma | -- Waiting for database... pleroma | pleroma-db:5432 - accepting connections pleroma | -- Running migrations... pleroma | ERROR! Config provider Pleroma.Config.ReleaseRuntimeProvider failed with: pleroma | ** (RuntimeError) Configuration at /etc/pleroma/config.exs has world-permissions, execute the following: chmod o= /etc/pleroma/config.exs pleroma | lib/pleroma/config/release_runtime_provider.ex:27: Pleroma.Config.ReleaseRuntimeProvider.load/2 pleroma | (elixir 1.11.4) lib/config/provider.ex:347: anonymous fn/2 in Config.Provider.run_providers/2 pleroma | (elixir 1.11.4) lib/enum.ex:2193: Enum."-reduce/3-lists^foldl/2-0-"/3 pleroma | (elixir 1.11.4) lib/config/provider.ex:204: Config.Provider.boot_providers/4 pleroma | :init.eval_script/2 pleroma | :init.do_boot/3 pleroma | pleroma | pleroma | {"init terminating in do_boot",{#{'__exception__'=>true,'__struct__'=>'Elixir.RuntimeError',message=><<"Configuration pleroma | at /e pleroma | tc pleroma | /pleroma/config pleroma | .exs has w pleroma | orld-pe pleroma | rmission pleroma | s, execute the pleroma | following: ch pleroma | mod o= /etc/ pleroma | pleroma/c pleroma | onfig. pleroma | exs">>} pleroma | ,[{'Elixir.Pleroma.Conf pleroma | ig.ReleaseRuntimeProvider',load,2,[{file,"lib/pleroma/config/release_runtime_provider.ex"},{line,27}]},{'Elixir. pleroma | Config.Pro pleroma | vider', pleroma | '-run_p pleroma | rovider pleroma | s/2- pleroma | fun pleroma | -0 pleroma | -',2,[{ pleroma | file, pleroma | "lib pleroma | /con pleroma | fig/provid pleroma | er.ex"} pleroma | ,{line,347}]},{'El pleroma | ixir.Enum','-reduce/3-l pleroma | ists^foldl/2-0 pleroma | -',3,[{f pleroma | ile,"lib/ pleroma | enum.ex"},{li pleroma | ne,2193}]}, pleroma | {'Elix pleroma | ir.Config pleroma | .Provid pleroma | er',bo pleroma | ot_prov pleroma | iders,4,[{ pleroma | file," pleroma | lib/con pleroma | fig/provi pleroma | der.ex"}, pleroma | {line,2 pleroma | 04}]},{in pleroma | it,eva pleroma | l_script, pleroma | 2,[]}, pleroma | {init, pleroma | do_boot,3 pleroma | ,[]}]} pleroma | } pleroma | init terminating in do_boot ( pleroma | {,[{Eli pleroma | xir.Ple pleroma | roma.Confi pleroma | g.Relea pleroma | seRunti pleroma | meProvi pleroma | der,lo pleroma | ad,2,[{_}, pleroma | {_}]}, pleroma | {Elixir pleroma | .Config pleroma | .Provider, pleroma | -run_provi pleroma | ders/2-f pleroma | un-0-,2 pleroma | ,[{_},{ pleroma | _}]},{Elix pleroma | ir.Enum pleroma | ,-reduce/ pleroma | 3-lists pleroma | ^foldl/2-0 pleroma | -,3,[{_ pleroma | },{_}]},{ pleroma | Elixir. pleroma | Config. pleroma | Provide pleroma | r,boot_ pleroma | provide pleroma | rs,4,[{_}, pleroma | {_}]},{in pleroma | it,eval_s pleroma | cript,2,[] pleroma | },{init pleroma | ,do_boo pleroma | t,3,[]} pleroma | ]}) pleroma | pleroma | Crash dump is being written to: pleroma | erl_crash.dump.. pleroma | . pleroma exited with code 0 ``` * I can not take a quick look if Pleroma is something for me or not. # What should happen * It should just work so that I can play around with Pleroma on localhost to see if it is something for me or not.
nloadholtes commented 2024-03-24 18:40:25 +00:00
Member
Copy link

I managed to get past this error by adjusting the owner/group of the config.exs file. On my local machine I did chmod -R 100:100 * to get everything in the environments and volumes directories. (I discovered this by overriding the entrypoint so I could look at the filesystem before it rebooted. The userid of pleroma on my local machine did not match what the container had, so as a quick-and-dirty hack I put my local files to be 100:100 which seemed to be enough to get past the strict permissions check.)

HOWEVER... now it fails with:

pleroma       | pleroma-db:5432 - accepting connections
pleroma       | -- Running migrations...
pleroma       | ** (EXIT from #PID<0.94.0>) shutdown

I got into the running container and tried manually running ./pleroma_ctl migrate and it gave the same output.

I'm curious what's causing this, but it is also too nice outside for me to be spending any more time on this today. 😄

I managed to get past this error by adjusting the owner/group of the config.exs file. On my local machine I did `chmod -R 100:100 *` to get everything in the environments and volumes directories. (I discovered this by overriding the entrypoint so I could look at the filesystem before it rebooted. The userid of pleroma on my local machine did not match what the container had, so as a quick-and-dirty hack I put my local files to be 100:100 which seemed to be enough to get past the strict permissions check.) HOWEVER... now it fails with: ``` pleroma | pleroma-db:5432 - accepting connections pleroma | -- Running migrations... pleroma | ** (EXIT from #PID<0.94.0>) shutdown ``` I got into the running container and tried manually running `./pleroma_ctl migrate` and it gave the same output. I'm curious what's causing this, but it is also too nice outside for me to be spending any more time on this today. :smile:
lamemakes commented 2024-05-14 03:03:49 +00:00
Member
Copy link

@nloadholtes hey! any chance you were able to resolve this? currently battling the same thing

@nloadholtes hey! any chance you were able to resolve this? currently battling the same thing
nloadholtes commented 2024-05-14 20:15:36 +00:00
Member
Copy link

@lamemakes Sadly no. 😞 I got side tracked by some other unrelated issues. I did run into something similar to this on another project, the problem/solution there was to make sure that the UID being set in the Dockerfile was not being overridden. I don't remember checking that on this one, so that could be something to check

@lamemakes Sadly no. :disappointed: I got side tracked by some other unrelated issues. I did run into something similar to this on another project, the problem/solution there was to make sure that the UID being set in the Dockerfile was not being overridden. I don't remember checking that on this one, so that could be something to check
lamemakes commented 2024-05-20 01:47:02 +00:00
Member
Copy link

@nloadholtes bummer! I stepped away for a bit but am still striking out. I'm running a rootless docker and am wondering that's a factor. will update if I find a fix

@nloadholtes bummer! I stepped away for a bit but am still striking out. I'm running a rootless docker and am wondering that's a factor. will update if I find a fix
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
gitlab-mr-iid-2
gitlab-mr-iid-1
No results found.
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
3 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
pleroma/pleroma-docker-compose#3
No description provided.