ArmyCyberInstitute / cmgr

CTF Challenge Manager
Apache License 2.0
17 stars 9 forks source link

Unable to test examples on cmgr #12

Closed boomcan90 closed 3 years ago

boomcan90 commented 3 years ago

Following the instructions to setup the basic instance and test the examples, I am getting the following errors:

$ sudo ./cmgr test --require-solve
cmgr: [ERROR:  failed to build image: The command '/bin/sh -c apt-get install -y ssh' returned a non-zero code: 100]
error (cmgr/examples/aptitude-and-privileges): could not build: failed to build image: The command '/bin/sh -c apt-get install -y ssh' returned a non-zero code: 100
cmgr: [ERROR:  failed to build image: The command '/bin/sh -c apt-get -y install build-essential' returned a non-zero code: 100]
error (cmgr/examples/binex101): could not build: failed to build image: The command '/bin/sh -c apt-get -y install build-essential' returned a non-zero code: 100
cmgr: [ERROR:  failed to build image: The command '/bin/sh -c apt-get -y install python3-pip build-essential' returned a non-zero code: 100]
error (cmgr/examples/custom-socat): solver failed: failed to build image: The command '/bin/sh -c apt-get -y install python3-pip build-essential' returned a non-zero code: 100
cmgr: [ERROR:  failed to build image: The command '/bin/sh -c apt-get -y install python3-pip build-essential' returned a non-zero code: 100]
error (cmgr/examples/flask--sqlite): could not build: failed to build image: The command '/bin/sh -c apt-get -y install python3-pip build-essential' returned a non-zero code: 100
cmgr: [ERROR:  failed to build image: The command '/bin/sh -c apt-get -y install build-essential' returned a non-zero code: 100]
error (cmgr/examples/lockbox): could not build: failed to build image: The command '/bin/sh -c apt-get -y install build-essential' returned a non-zero code: 100
cmgr: [ERROR:  failed to build image: The command '/bin/sh -c apt-get -y install python3-pip build-essential' returned a non-zero code: 100]
error (cmgr/examples/node-server): solver failed: failed to build image: The command '/bin/sh -c apt-get -y install python3-pip build-essential' returned a non-zero code: 100
cmgr: [ERROR:  failed to build image: The command '/bin/sh -c apt-get -y install php' returned a non-zero code: 100]
error (cmgr/examples/php-sqlite): could not build: failed to build image: The command '/bin/sh -c apt-get -y install php' returned a non-zero code: 100
cmgr: [ERROR:  failed to build image: The command '/bin/sh -c apt-get -y install python3-pip build-essential' returned a non-zero code: 100]
error (cmgr/examples/re101): could not build: failed to build image: The command '/bin/sh -c apt-get -y install python3-pip build-essential' returned a non-zero code: 100
cmgr: [ERROR:  failed to build image: The command '/bin/sh -c apt-get -y install python3-pip build-essential' returned a non-zero code: 100]
error (cmgr/examples/read-it-and-weep): could not build: failed to build image: The command '/bin/sh -c apt-get -y install python3-pip build-essential' returned a non-zero code: 100
cmgr: [ERROR:  failed to build image: The command '/bin/sh -c apt-get -y install build-essential' returned a non-zero code: 100]
error (cmgr/examples/recovery-and-identification): could not build: failed to build image: The command '/bin/sh -c apt-get -y install build-essential' returned a non-zero code: 100
cmgr: [ERROR:  failed to build image: The command '/bin/sh -c apt-get -y install python3-pip build-essential' returned a non-zero code: 100]
error (hacksport/ecb-1): solver failed: failed to build image: The command '/bin/sh -c apt-get -y install python3-pip build-essential' returned a non-zero code: 100

While it seems to be an issue with networking within docker, spinning up other instances and doing RUN apt-get update && apt-get install -y <packages> works fine.

Distro information:

$ uname -a
Linux ubuntu 5.4.0-53-generic #59-Ubuntu SMP Wed Oct 21 09:38:44 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
$ docker --version
Docker version 19.03.13, build 4484c46d9d
boomcan90 commented 3 years ago

Closing - was a docker hygiene issue.