Replies: 14 comments 3 replies
-
fwiw I can reproduce the same issue w/ the following docker-compose.yml: on a clean machine.
|
Beta Was this translation helpful? Give feedback.
-
Thanks, that's interesting, it's coming up with an SQLite database deadlock; I'll work out what's going on there. |
Beta Was this translation helpful? Give feedback.
-
It would be interesting to know whether you get the same problem if you go back a version or two... |
Beta Was this translation helpful? Give feedback.
-
Running the above docker-compose with the image set to Digging into it more, there was a file permissions issue regarding the database it made - only writable by root according to ls -l, which is what was making it hang. Breaking both it and the archive directory (just in case) into submission via chmod seems to have done the trick to get it to boot, but it's still having a few issues, presumably file/dir perms related. While it's not a loop anymore (and I can log in, use the UI), it fails to upload any files. Relevant logs from the (fixed perms) run: There's no logs for the failed upload, from what I can tell. Here's the browser error, if that helps? I'm not sure if this is the same issue as the OP now that I've gotten the perms issue out of the way, but it might be? |
Beta Was this translation helpful? Give feedback.
-
Weirdly enough, making collections works without a hitch, it's just having issues uploading. |
Beta Was this translation helpful? Give feedback.
-
If your upload problem is in |
Beta Was this translation helpful? Give feedback.
-
Upload issue WAS in /edge, thanks for pointing that out. Seems to work! woohoo, Now I just gotta figure out how to properly use it Good luck, and thanks for your work! |
Beta Was this translation helpful? Give feedback.
-
@Adam-Kay does what @SilverbackConnor mentioned about permissions match your situation, by any chance? |
Beta Was this translation helpful? Give feedback.
-
My case is a little different, since my directory is a networked location added via |
Beta Was this translation helpful? Give feedback.
-
OK, I'll leave this open and take a closer look. Did you try switching to an older version, perhaps v0.76.0? I think it might be a problem with doing an upgrade from older versions straight to v0.77.0, so it would be useful to know if that helps. |
Beta Was this translation helpful? Give feedback.
-
Just switched to
|
Beta Was this translation helpful? Give feedback.
-
OK, thanks for trying it. I'll dig in. |
Beta Was this translation helpful? Give feedback.
-
@Adam-Kay So, I've just run up a fresh instance of |
Beta Was this translation helpful? Give feedback.
-
Hi, i have the same/similar problem. When i start docker compose up i get into a loop and website is not accessible. I outcommented (is this a word?) the puid/pgid and deleted the database and config folders. Now the website startet but its saying: "Manyfold runs as root... dangerous..." Hope this helps somehow. ps: i ran before the standard version (just till starting screen) but then i wanted to not have to login and tried the solo. |
Beta Was this translation helpful? Give feedback.
-
Describe the bug
Having a problem when creating the Docker instance provided here. I'm using the Solo image and when looking in the logs, I just get a looping error and can't access the Web interface. I'm a little new to Docker but as far as I can tell everything should be working - or I have misconfigured something.
To Reproduce
Log error
Full log
_manyfold_logs.txt
(latest 1000 lines)
Additional context
I'm using Portainer, but that's just a nice GUI on top of Docker so shouldn't be affecting anything.
Beta Was this translation helpful? Give feedback.
All reactions