[
https://issues.apache.org/jira/browse/NUTCH-3098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adrian Kunz updated NUTCH-3098:
-------------------------------
Description:
The commands in the apache/nutch Docker Readme do not work.
{code:java}
$ docker run -t -i -p 8080:8080 -p 8081:8081 --name nutchcontainer apache/nutch
# inside the container shell (note no -d):
~ # cat /tmp/supervisord.log
cat: can't open '/tmp/supervisord.log': No such file or directory
{code}
Outside the container shell:
{code:java}
$ curl http://localhost:8080/admin
curl: (52) Empty reply from server{code}
If I built from source (which takes almost 10 minutes, btw), it seems to work:
{code:java}
docker run -it -p 8180:8080 -p 8181:8081 --name nutch <my-registry>/apache/nutch
WARNING: The requested image's platform (linux/amd64) does not match the
detected host platform (linux/arm64/v8) and no specific platform was requested
2024-12-09 15:53:15,432 INFO Set uid to user 0 succeeded
2024-12-09 15:53:15,436 INFO supervisord started with pid 1
2024-12-09 15:53:16,440 INFO spawned: 'nutchserver' with pid 7
2024-12-09 15:53:16,442 INFO spawned: 'nutchwebapp' with pid 8
2024-12-09 15:53:17,443 INFO success: nutchserver entered RUNNING state,
process has stayed up for > than 0 seconds (startsecs)
2024-12-09 15:53:17,443 INFO success: nutchwebapp entered RUNNING state,
process has stayed up for > than 0 seconds (startsecs){code}
Now I can access the server:
{code:java}
$ curl http://localhost:8181/admin
{"startDate":1733759756634,"configuration":["default"],"jobs":[],"runningJobs":[]}
$ curl http://localhost:8180
$ # but not the web interface{code}
Another thing:
The Readme seems contradictory in it's use of ports:
{code:java}
You can now access the webapp at `http://localhost:8080` and you can interact
with the REST API e.g.
```bash curl http://localhost:8080/admin
{"startDate":1625118207995,"configuration":["default"],"jobs":[],"runningJobs":[]}
```{code}
Here 8080 is both the web app and the server port, vs the default suggestion,
where 8081 is server and 8080 is web app:
{code:java}
docker build -t apache/nutch . --build-arg BUILD_MODE=2 --build-arg
SERVER_PORT=8081 --build-arg SERVER_HOST=0.0.0.0 --build-arg
WEBAPP_PORT=8080{code}
was:
The commands in the apache/nutch Docker Readme do not work.
{code:java}
$ docker run -t -i -p 8080:8080 -p 8081:8081 --name nutchcontainer apache/nutch
# inside the container shell (note no -d):
~ # cat /tmp/supervisord.log
cat: can't open '/tmp/supervisord.log': No such file or directory
{code}
Outside the container shell:
{code:java}
$ curl http://localhost:8080/admin
curl: (52) Empty reply from server{code}
If I built from source (which takes an enormous amount of time, btw), it seems
to work:
{code:java}
docker run -it -p 8180:8080 -p 8181:8081 --name nutch <my-registry>/apache/nutch
WARNING: The requested image's platform (linux/amd64) does not match the
detected host platform (linux/arm64/v8) and no specific platform was requested
2024-12-09 15:53:15,432 INFO Set uid to user 0 succeeded
2024-12-09 15:53:15,436 INFO supervisord started with pid 1
2024-12-09 15:53:16,440 INFO spawned: 'nutchserver' with pid 7
2024-12-09 15:53:16,442 INFO spawned: 'nutchwebapp' with pid 8
2024-12-09 15:53:17,443 INFO success: nutchserver entered RUNNING state,
process has stayed up for > than 0 seconds (startsecs)
2024-12-09 15:53:17,443 INFO success: nutchwebapp entered RUNNING state,
process has stayed up for > than 0 seconds (startsecs){code}
Now I can access the server:
{code:java}
$ curl http://localhost:8181/admin
{"startDate":1733759756634,"configuration":["default"],"jobs":[],"runningJobs":[]}
$ curl http://localhost:8180
$ # but not the web interface{code}
Another thing:
The Readme seems contradictory in it's use of ports:
{code:java}
You can now access the webapp at `http://localhost:8080` and you can interact
with the REST API e.g.
```bash curl http://localhost:8080/admin
{"startDate":1625118207995,"configuration":["default"],"jobs":[],"runningJobs":[]}
```{code}
Here 8080 is both the web app and the server port, vs the default suggestion,
where 8081 is server and 8080 is web app:
{code:java}
docker build -t apache/nutch . --build-arg BUILD_MODE=2 --build-arg
SERVER_PORT=8081 --build-arg SERVER_HOST=0.0.0.0 --build-arg
WEBAPP_PORT=8080{code}
> Docker Setup from Readme does not work
> --------------------------------------
>
> Key: NUTCH-3098
> URL: https://issues.apache.org/jira/browse/NUTCH-3098
> Project: Nutch
> Issue Type: Bug
> Components: docker
> Reporter: Adrian Kunz
> Priority: Major
>
> The commands in the apache/nutch Docker Readme do not work.
> {code:java}
> $ docker run -t -i -p 8080:8080 -p 8081:8081 --name nutchcontainer
> apache/nutch
> # inside the container shell (note no -d):
> ~ # cat /tmp/supervisord.log
> cat: can't open '/tmp/supervisord.log': No such file or directory
> {code}
> Outside the container shell:
> {code:java}
> $ curl http://localhost:8080/admin
> curl: (52) Empty reply from server{code}
> If I built from source (which takes almost 10 minutes, btw), it seems to work:
> {code:java}
> docker run -it -p 8180:8080 -p 8181:8081 --name nutch
> <my-registry>/apache/nutch
> WARNING: The requested image's platform (linux/amd64) does not match the
> detected host platform (linux/arm64/v8) and no specific platform was requested
> 2024-12-09 15:53:15,432 INFO Set uid to user 0 succeeded
> 2024-12-09 15:53:15,436 INFO supervisord started with pid 1
> 2024-12-09 15:53:16,440 INFO spawned: 'nutchserver' with pid 7
> 2024-12-09 15:53:16,442 INFO spawned: 'nutchwebapp' with pid 8
> 2024-12-09 15:53:17,443 INFO success: nutchserver entered RUNNING state,
> process has stayed up for > than 0 seconds (startsecs)
> 2024-12-09 15:53:17,443 INFO success: nutchwebapp entered RUNNING state,
> process has stayed up for > than 0 seconds (startsecs){code}
> Now I can access the server:
> {code:java}
> $ curl http://localhost:8181/admin
> {"startDate":1733759756634,"configuration":["default"],"jobs":[],"runningJobs":[]}
> $ curl http://localhost:8180
> $ # but not the web interface{code}
> Another thing:
> The Readme seems contradictory in it's use of ports:
>
> {code:java}
> You can now access the webapp at `http://localhost:8080` and you can interact
> with the REST API e.g.
> ```bash curl http://localhost:8080/admin
> {"startDate":1625118207995,"configuration":["default"],"jobs":[],"runningJobs":[]}
> ```{code}
>
> Here 8080 is both the web app and the server port, vs the default suggestion,
> where 8081 is server and 8080 is web app:
> {code:java}
> docker build -t apache/nutch . --build-arg BUILD_MODE=2 --build-arg
> SERVER_PORT=8081 --build-arg SERVER_HOST=0.0.0.0 --build-arg
> WEBAPP_PORT=8080{code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
