-
Notifications
You must be signed in to change notification settings - Fork 54
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
XBS-API container continually restarting and will not remain connected to docker stack network. #15
Comments
Also, just to provide further info this is what is in my settings.json:
|
I am also having the same issue |
I am having the same issue. While I was trying to find the syntax for settings.json, I noticed that https://github.com/xbrowsersync/api-docker doesn’t contain any settings.default,json file (as referenced in the (documentation)[https://github.com/xbrowsersync/api#3-modify-configuration-settings] (pt 4.). I tried setting server.behindProxy to true, but it didn’t help. |
I am also having issues with it constantly crashing, but in my kubernetes cluster, but not my swarm cluster... The following
Also here is my yaml files for kub if people wanted to check those |
https://github.com/xbrowsersync/api-docker/blob/master/settings.json |
@xthursdayx are you able to run the API on it's own (not with docker)? |
I have tried to run in a debug mode but no option exists to get any out before the container restarts. |
Can you run the following command and paste the output here:
Edit: also, to prevent the container from constantly restarting, update line 33 of |
Hello. I encountered a similar problem, but under different conditions.
My settings.
settings.json:
docker-compose.yml:
I didn't change the files, healthcheck.js and mongoconfig.js. |
I figured out what the problem is, maybe it will help someone else too. |
You have a trailing comma in your json which would be a syntax error (for JSON), but my files are otherwise the same as yours and xbs-api just won't start. I did the same as is recommended in #13 |
I didn't want to highjack this issue: #13 but I too am trying to run the xbrowsersync api-docker stack without caddy, so that I can then use NGINX to reverse proxy the container, since I already use it for other containers, but am running into some issues.
I've tried creating and starting the stack with the
docker-compose.yml
(only modified to change the mounted port) you posted in issue #13 usingdocker-compose up -d
and have also tried creating the stack via Portainer using the docker-compose as a template. I've also tried just creating the api-docker container manually with adocker run
command including all of the necessary variables and a separately created MongoDB.For some reason in each case the MongoDB container and xbs-api container are created and the db container seems to function normally, but the xbs-api container continually restarts and won't stay connected to the xbs docker network that is created. I've tried changing the healthcheck interval, timeout length, retries, and start period, and also tried removing the healthcheck entirely, just to see, but it found the same issue, though I couldn't tell if the container was restarting or just refusing to connect to the xbrowsersync docker network and mount the 8080 port.
I am unable to access the internal container logs because the container is continually restarting and there isn't anything in the external logs for the xbs-api container. The most information I could find was by inspecting the container in Portainer, which listed this information about the container:
I am trying to start the container on unRAID which is an OS based on Slackware. Any advice or suggestion would bee much appreciated. Thanks!
The text was updated successfully, but these errors were encountered: