You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've tried several times to run Nuxeo through the docker container, following the documentation laid out here, but each time I end up with no response from http://localhost:8080/nuxeo (ERR_NO_DATA in Chrome).
There are no errors in any of the logs, and when I run a curl on localhost:8080 inside the container the connection is refused, so it seems like there's nothing actually listening on 8080.
This is happening on OSX Mojave, with Docker Desktop CE 2.1.0.1 (Docker Engine 19.03.1).
For reference, here's the terminal output from setting up the container:
➜ ~ docker run -d --name nuxeo -p 8080:8080 nuxeo/nuxeo:discover-ft
89b5dc0d84c33aeaabc776695d147dc3a029778f917b720a6e9fe2256ead7523
➜ ~ docker exec -ti nuxeo bin/nuxeoctl register
Nuxeo home: /opt/nuxeo/server
Nuxeo configuration: /etc/nuxeo/nuxeo.conf
Include template: /opt/nuxeo/server/templates/common-base
Include template: /opt/nuxeo/server/templates/common
Include template: /opt/nuxeo/server/templates/default
Include template: /opt/nuxeo/server/templates/docker
Username: ****
Please enter your password:
Instance type (dev|preprod|prod): [dev]
Description:
Server registered to **** for project ****
****
****
Type: dev
Description:
➜ ~ docker exec -ti nuxeo bin/nuxeoctl stop
Nuxeo home: /opt/nuxeo/server
Nuxeo configuration: /etc/nuxeo/nuxeo.conf
Include template: /opt/nuxeo/server/templates/common-base
Include template: /opt/nuxeo/server/templates/common
Include template: /opt/nuxeo/server/templates/default
Include template: /opt/nuxeo/server/templates/docker
Stopping server....Server stopped.
➜ ~ docker exec -ti nuxeo bin/nuxeoctl mp-list
Nuxeo home: /opt/nuxeo/server
Nuxeo configuration: /etc/nuxeo/nuxeo.conf
Include template: /opt/nuxeo/server/templates/common-base
Include template: /opt/nuxeo/server/templates/common
Include template: /opt/nuxeo/server/templates/default
Include template: /opt/nuxeo/server/templates/docker
Local packages:
addon downloaded nuxeo-dam (id: nuxeo-dam-6.4.3)
addon downloaded nuxeo-drive (id: nuxeo-drive-1.8.5)
addon downloaded nuxeo-liveconnect (id: nuxeo-liveconnect-1.3.3)
addon downloaded nuxeo-showcase-content (id: nuxeo-showcase-content-1.3.3)
addon downloaded nuxeo-spreadsheet (id: nuxeo-spreadsheet-1.4.3)
addon downloaded nuxeo-template-rendering (id: nuxeo-template-rendering-6.8.3)
addon downloaded nuxeo-vision (id: nuxeo-vision-1.3.4)
addon downloaded nuxeo-web-ui (id: nuxeo-web-ui-2.4.0)
➜ ~ docker exec -ti nuxeo bin/nuxeoctl mp-init
Nuxeo home: /opt/nuxeo/server
Nuxeo configuration: /etc/nuxeo/nuxeo.conf
Include template: /opt/nuxeo/server/templates/common-base
Include template: /opt/nuxeo/server/templates/common
Include template: /opt/nuxeo/server/templates/default
Include template: /opt/nuxeo/server/templates/docker
➜ ~ docker exec -ti nuxeo bin/nuxeoctl mp-install nuxeo-dam nuxeo-web-ui
Nuxeo home: /opt/nuxeo/server
Nuxeo configuration: /etc/nuxeo/nuxeo.conf
Include template: /opt/nuxeo/server/templates/common-base
Include template: /opt/nuxeo/server/templates/common
Include template: /opt/nuxeo/server/templates/default
Include template: /opt/nuxeo/server/templates/docker
Optional dependencies [nuxeo-jsf-ui] will be ignored for 'nuxeo-dam-6.4.3'.
Dependency resolution:
Installation order (2): nuxeo-web-ui-2.4.0/nuxeo-dam-6.4.3
Local packages to install (2): nuxeo-web-ui:2.4.0, nuxeo-dam:6.4.3
Do you want to continue (yes/no)? [yes]
Installing nuxeo-web-ui-2.4.0
Installing nuxeo-dam-6.4.3
➜ ~ docker exec -ti nuxeo bin/nuxeoctl start
Nuxeo home: /opt/nuxeo/server
Nuxeo configuration: /etc/nuxeo/nuxeo.conf
Include template: /opt/nuxeo/server/templates/common-base
Include template: /opt/nuxeo/server/templates/common
Include template: /opt/nuxeo/server/templates/default
Include template: /opt/nuxeo/server/templates/docker
No current configuration, generating files...
Configuration files generated.
Server started with process ID 762.
Go to http://localhost:8080/nuxeo
EDIT: On closer inspection, it seems the server may be crashing or just not starting up at all.
➜ ~ docker exec -ti nuxeo bin/nuxeoctl start
Nuxeo home: /opt/nuxeo/server
Nuxeo configuration: /etc/nuxeo/nuxeo.conf
Include template: /opt/nuxeo/server/templates/common-base
Include template: /opt/nuxeo/server/templates/common
Include template: /opt/nuxeo/server/templates/default
Include template: /opt/nuxeo/server/templates/docker
Configuration files generation (nuxeo.force.generation=true)...
Configuration files generated.
Server started with process ID 832.
.........
======================================================================
= Component Loading Status: Pending: 0 / Missing: 0 / Unstarted: 0 / Total: 546
======================================================================
Started in 0min18s
Go to http://localhost:8080/nuxeo
➜ ~ docker exec -ti nuxeo ps wuax
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
nuxeo 1 0.0 0.0 19764 3340 ? Ss 18:33 0:00 /bin/bash /opt/nuxeo/server/bin/nuxeoctl console
nuxeo 80 1.7 1.4 5024012 116268 ? Sl 18:33 0:01 java -Xbootclasspath/a:/usr/local/openjdk-8/lib/tools.jar -Dlaunche
nuxeo 1099 0.0 0.0 38380 3104 pts/0 Rs+ 18:35 0:00 ps wuax
The text was updated successfully, but these errors were encountered:
It turns out that starting the server with the -ti option for docker exec is what was causing the issue - the process was being killed when the command was finished.
I've tried several times to run Nuxeo through the docker container, following the documentation laid out here, but each time I end up with no response from http://localhost:8080/nuxeo (ERR_NO_DATA in Chrome).
There are no errors in any of the logs, and when I run a curl on localhost:8080 inside the container the connection is refused, so it seems like there's nothing actually listening on 8080.
This is happening on OSX Mojave, with Docker Desktop CE 2.1.0.1 (Docker Engine 19.03.1).
For reference, here's the terminal output from setting up the container:
EDIT: On closer inspection, it seems the server may be crashing or just not starting up at all.
The text was updated successfully, but these errors were encountered: