docker run errors

[girs1982]

[ERROR] post shutdown: accept tcp [::]:8080: use of closed network connection [CRITICAL] command exited during start up 2018/06/01 16:37:43 command exited during start up

run docker run -p 8080:8080 -e "MB_KEY=$MB_KEY" machinebox/facebox

[aaronedell]

This error is almost always due to not giving Docker enough RAM of CPU resources to run the box. Start with 2GB of RAM and 2CPUs and see if that improves.

[girs1982]

no i have 8gb memory and 6 core amd

[girs1982]

how it done?

[aaronedell]

Can you give us some more details about the environment and which box you're using? Where is this running, when does this error occur, etc.

Also, please run $ docker ps after running the box but before it shuts down and report the results here.

[girs1982]

Ubuntu 18 CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES root@gansta-desktop:/home/gansta#

root@gansta-desktop:/home/gansta# docker run -p 8080:8080 -e "MB_KEY=$MB_KEY" machinebox/facebox docker run -p 8080:8080 -e "MB_KEY=$MB_KEY" machinebox/facebox 2018/06/01 16:46:05 Number of MB_WORKERS is set to 4 [INFO] starting...

    Welcome to Facebox by Machine Box
    (facebox development)

    Visit the console to see what this box can do:
    http://localhost:8080

    If you have any questions or feedback, get in touch:
    https://machinebox.io/contact

    Please consider buying a subscription:
    https://machinebox.io/#pricing

    Report bugs and issues:
    https://github.com/machinebox/issues

    Tell us what you build on Twitter @machineboxio

[ERROR] post shutdown: accept tcp [::]:8080: use of closed network connection [CRITICAL] command exited during start up 2018/06/01 16:46:16 command exited during start up root@gansta-desktop:/home/gansta# docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES

CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES root@gansta-desktop:/home/gansta# docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 2471ff259449 machinebox/facebox "/app/facebox" 3 seconds ago Up Less than a second 0.0.0.0:8080->8080/tcp sharp_wescoff

[girs1982]

CONTAINER CPU % MEM USAGE / LIMIT MEM % NET I/O BLOCK I/O PIDS 797b16df63ec 10.50% 9.625MiB / 7.544GiB 0.12% 9.82kB / 2kB 0B / 0B 13

CONTAINER CPU % MEM USAGE / LIMIT MEM % NET I/O BLOCK I/O PIDS 27b70e68d12a 0.00% 3.094MiB / 7.544GiB 0.04% 1.22kB / 336B 0B / 0B 7

no i dont know how it do 2cpu and 2gb,how? i have ubuntu ,ubuntu no have graf interface

[aaronedell]

Which box are you using?

[girs1982]

MB_KEY=ommit docker run -p 8080:8080 -e "MB_KEY=$MB_KEY" machinebox/facebox

i install all ,docker ubuntu 18

[dahernan]

Does your CPU supports AVX and SSE instructions? Usually is not a problem but it could be on old CPUs

[girs1982]

it not cpu phenom 2 x6 i have

[dahernan]

Yeah i think that is the problem, I'll try to look it next week, but disabling the instructions I'm guessing that it would be really slow to run, that could be unusable

[girs1982]

i will wait

[elbogi]

I am experiencing the same issue. Running docker-compose with the following config:

facebox:
  image: machinebox/facebox:latest
  container_name: facebox
  restart: unless-stopped
  ports:
    - 8080:8080
  volumes:
    - /home/$USER/docker_files/facebox:/facebox
  environment:
    - MB_KEY= <my registered key>

Running Ubuntu Server 16.04 on a machine with an i7 CPU / 8 GB RAM.

After starting with docker-compose up facebox I get the following error:

Number of MB_WORKERS is set to 4
[INFO]     starting...
<common info removed>
[ERROR]    post shutdown: accept tcp [::]:8080: use of closed network connection
[CRITICAL]    command exited during start up
command exited during start up
exited with code 1

[nunofgs]

I'm also experiencing the same thing with a Celeron N3150 (4 cores) / 8GB RAM. Admittedly it's a slow machine but just wanted to get a feel for the software.

[dahernan]

Sorry facebox is compiled with AVX support, because is around 10x quicker, and all of the current costumers run the box in CPUs with that capability.

We may release a version compiled without AVX flags, but given that we are a small team, and that increase the maintenance of the images, and running an instance of the box without AVX support in a machine that is already slow, is probably not a good idea, so is not a priority right now.

[jghaanstra]

Got the same issue. The container has 8GB available, yet I get the message that the container does not have enough ram to start. Obviously this is not the actual reason that keeps the container from starting up. Question is, what is wrong and how do I fix it.

2018-06-14 17:35:24|stdout|[INFO]     starting...|
|2018-06-14 17:35:23|stdout|2018/06/14 17:35:23 Number of MB_WORKERS is set to 4|
|2018-06-14 17:35:20|stdout|2018/06/14 17:35:20 command exited during start up, make sure the container has enough RAM available to start, check out https://machinebox.io/docs/setup/docker#minimum-requirements|
|2018-06-14 17:35:20|stdout|[CRITICAL]    command exited during start up, make sure the container has enough RAM available to start, check out https://machinebox.io/docs/setup/docker#minimum-requirements|
|2018-06-14 17:35:20|stdout|[ERROR]    post shutdown: accept tcp [::]:8080: use of closed network connection|

[matryer]

@jghaanstra what machine are you running this on?

[girs1982]

ubuntu phenom 2 x6 8gb

[jghaanstra]

@matryer I'm trying to run it on an Synology DS216++ with upgraded RAM to 8GB. A previous version of the Facebox docker container was working for somebody else on this machine. Earlier this evening he confirmed his container wont start anymore with the same error after pulling in latest version of the container. So there is definitely something wrong with the latest version of the docker container. Unfortunately Machinebox does not seem to keep older version available on Docker hub so there is no way in testing for me.

[jackjohnsonuk]

same for me running on unRaid - 32GB of Ram on an r710 ! 😢 hoping to get it working soon though, I'm excited for the product.

[matryer]

We’re working on trying to solve this. @dahernan might have some news next week.

[dahernan]

This image should work on CPUs without AVX support, please use this image, instead. $ docker pull machinebox/facebox_noavx A big disclaimer using this image is that, we have no plans to maintain, or support this image with bug fixes and new features, given that is high cost for us to do that at this point.

[girs1982]

i done it self https://www.youtube.com/watch?v=VIcQSBqAQm0

my face detect server,for my terminator)))

[nunofgs]

While it does work, only a facebox image is available. I'm sad 😢

[anmolah]

@dahernan , I am working on a proof of concept project and need to showcase this on my machine with no avx support. I would really appreciate an update to the facebox_noavx image with the new save/restore state feature to complete my work. I completely understand this is not official or supported and am fine with an unofficial image for testing.

Thank you in advance.

[dahernan]

@anmolah I've just updated the image, can you try it and let me know if is working?

[anmolah]

@dahernan that was quick 🥇

Appreciate it.