-
Notifications
You must be signed in to change notification settings - Fork 64
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
404 Not Found for 127.0.0.1/boincserver #53
Comments
What's the host system you're running this on? Are you running Docker via Docker Machine or maybe Docker for Win or Mac by chance? |
I'm running on Mac Mojave 10.14.2, using Docker for Mac. |
I'm guessing its a IP address / port fowarding problem. I've never played with this on Mac myself. According to https://docs.docker.com/docker-for-mac/networking/ this should work. Does the example in that link work for you? Mainly if you stop boinc-server-docker then run |
I doubt it's a IP address / port forwarding problem, I don't have any services running on port 80 other than the apache server in the docker container. When I run
I do see an nginx welcome page when I run |
Ah you're right, I missed above that it was at least connecting to the server. What happens if you do
Anything of note in |
Here's what I have:
Looks about the same. For the supervisor logs:
|
I managed to hack a solution, maybe it will help you find the root problem. I temporarily fixed it by making a symlink of the
|
Ah I should have guessed. The
but in the log you sent above, the line that says If I had to guess, I'd say its probably the In the meantime glad you found a workaround and thanks for helping track this down. |
Here is the log for supervisor:
I'm not sure how Mac Docker works, but as far as I know my Docker socket on my Mac is also on |
Looks like the problem is that |
Here's what I get
|
Can you find the group ID of your hosts |
Yeah, looks like the equivalent for Mac is the
I'll try it in the makeproject3 and see if it works. |
Inside the container its the Linux version of I think creating a |
I'm not sure what the right way is, but while waiting, I think the following workaround is better than making a symbolic link in the docker container. So, what I did was replace these lines: boinc-server-docker/images/apache/makeproject-step3.sh Lines 8 to 10 in a1512c1
With these lines:
Basically, hardcoding the group id for docker and changing the permissions for |
Can you double check this doesn't change the GID on the host system? If so do you want to make a PR for this? It seems like a nice solution. |
Just checked on Linux and it does change the host group, so I don't think its a viable option. |
That's odd, my
What if it only sets the group id to 999 if the current group id is 0? So something like:
|
Just letting you guys know I have the same problem on Windows. |
Thanks for the report. Let me know if you or @joeltio have any ideas on a permanent solution, I haven't had time to think about this more since the discussion above... |
So over the last few days, I have been trying to solve this problem. The /etc/apache2/ directory only exists once docker-compose finishes launching apache, not during the execution of 'supervisored.conf - project:start' So in order to solve this bug, you need to find a way to execute this line My current solution is to tack this code at the end of 'docker-compose.yml' THIS DOES NOT WORK YET |
Another solution is just to delete the following three lines: boinc-server-docker/images/apache/makeproject-step3.sh Lines 8 to 10 in a1512c1
however, with either this or your solution, boinc2docker jobs will not work. But we definitely should find a solution such that at the very least the server keeps working. |
I tried with this configuration and still I'm getting the error I'm using: Docker version 18.09.2, build 6247962 |
Can you double check everything rebuilt correctly after you deleted those lines? Running |
Oh, also, |
Hey everybody, I have the same problem with Docker Windows. |
Does #53 (comment) work for you? |
yes it works with that, but how about the above-mentioned problem? now I am facing this problem because I can't see my boinc2docker jobs ? |
I don't have a workaround that works with boinc2docker yet unfortunately. |
worked for me, how about adding it to the master branch so the project could work out of the box? |
git clone https://github.com/marius311/boinc-server-docker.git
cd boinc-server-docker and then run, docker-compose pull
docker-compose up -d
docker-compose exec apache bash
ln -s /home/boincadm/project/boincserver.httpd.conf /etc/apache2/conf-enabled/boincserver.httpd.conf
/etc/init.d/apache2 reload
bin/stop
bin/start These are the steps required to run boinc server. If you change the environment file then you need to change the boincserver to the env project name |
I had a similar problem running on Mac. |
@philldresser Im getting this issue on Mac as well. I'm trying to follow the steps you executed, but in addition to removing the version line from docker-compose.yaml, when or how did you execute the make project script. Did you run after doing docker-compose up -d, I mean, while the container were running? |
I am trying to setup a BOINC server but I am getting a 404 on http://127.0.0.1/boincserver:
However, I do not see anything suspicious when I start with
docker-compose
(log at the end of this post).I have tried running
docker-compose down -v
before running as well. Here are my docker and docker compose versions:Docker compose up log:
Do I need to add any files or anything for the path to work?
The text was updated successfully, but these errors were encountered: