glotcode / docker-run

Api for running untrusted code in containers
MIT License
107 stars 25 forks source link

No reply when accessing the container #7

Open kolya5544 opened 2 years ago

kolya5544 commented 2 years ago

Hello.

I am unable to access a Docker container running docker-run. I run Ubuntu 18.04 with Docker 20.10.14. My docker.env -> API_ACCESS_TOKEN=my-token RUN_MAX_EXECUTION_TIME=5 DOCKER_CONTAINER_NETWORK_DISABLED=false

And I use the command from example command in run.md: docker run --detach --restart=always --publish 8088:8088 --env-file docker.env glot/docker-run:latest

docker logs outputs: [2022-07-26T14:59:34Z INFO docker_run] Listening on 0.0.0.0:8088 with 10 worker threads, however I am unable to access the application, neither of these commands work: curl --header 'X-Access-Token: my-token' http://localhost:8088/version curl http://localhost:8088 curl --request POST --header 'X-Access-Token: my-token' --header 'Content-type: application/json' --data '{"image": "glot/python:latest", "payload": {"language": "python", "files": [{"name": "main.py", "content": "print(42)"}]}}' http://localhost:8088/run. All of them result in curl: (56) Recv failure: Connection reset by peer or curl: (52) Empty reply from server. Nothing is binded to 8088.

This is a result from docker ps -a: bc0d290fcc91 glot/docker-run:latest "/nix/store/mr0cg9ll…" 3 minutes ago Up 3 minutes 0.0.0.0:8088->8088/tcp, :::8088->8088/tcp angry_swartz

No iptables/ufw rules block access to the application. Other docker webapp containers (unrelated to docker-run) work fine. What can the problem be?

Changing NPROC limits to really high values doesn't fix the issue.