-
Notifications
You must be signed in to change notification settings - Fork 10
Can't get latest or unstable to run #7
Comments
I just tried cloning this repository and building the image myself. It does not work either, but this time the error is different:
The |
I tried finding out why s6 wasn't able to run |
Hello zerweck, it should not be required to put anything in the bind mount. Did you try without any bind mount ? (without any data persistence). It could be a permission issue with the volume mount. I'm unsure if doing W10>WSL2>docker>Wine can cause issue but you could try running the image on another setup. I didn't manage to reproduce your issue yet but I'm aware that my image could use some work.. it's kind of a mess for now I guess. Do tell me if you have any more details about your issue. |
Hi, I'm getting the exact same issue as zerweck, and I'm also running on a synology nas. I've tried as you said and without any of the folders mounted it DOES work properly. The issue occurs with any single one of the 5 folders mounted, not any particular one. |
Hey, I've reinstalled my os (Fedora) and now the container doesn't work...
docker compose:
|
Definitely correct me if I'm wrong but that does not seem a valid syntax for the volumes bind point. Shouldn't it be
I don't see why you added |
I may missunderstand the use. But with Fedora and Selinux I used :z or :Z... |
Thanks for linking. I actually searched it up before replying but i probably skipped that.
Thanks for correcting me and as you say it's probably not what causes the issue. I was just wondering. Technically this docker-compose uses a service does it not? Honestly I'd try a path that has not been formatted by other container just for the shake of it if you're interested. |
I'm currently restructureing my server, so I'm down to try some things. I'll update tomorrow :) |
setting up a test inviroment with debian, works. Maybe a Fedora/Selinux problem? |
another update Using Debian and my old folders, I needed to delete my wine folder. Now it seems to work |
I've changed my server to debian and once again having this issue... even without volume mapping I'm facing this issue! |
I'll take a look |
Can you guys try banhcanh/docker-fmd2:kasm-v2 ? it's cleaned up, should be much better, even though the image might be heavier. I don't have a ci pipeline for this project so the versioning and all is manual sorry about that. |
I got it working, and even with my current setting and stuff migrated to userdata! I just added a volume for the modules, so they are not redownloaded every time. Opened pull request for that! Thanks for putting in some work! |
This is my current compose file.
|
I tried pulling both tagged versions from dockerhub, but both show the following behavior:
This repeats forever. It happens after a clean pull, using WSL2 on Windows 10 and the same happens on my Synology NAS.
I did nothing but create empty folders for all the bind mounts listed in the compose file, pulled the image and ran
docker-compose up
.Do you have any ideas? Is there anything that should be put into the bind mount folders before running the container?
The text was updated successfully, but these errors were encountered: