While building the teamserver docker container with docker build -t havoc-teamserver ., the user would face errors on line 58 for two major reasons:
the teamserver folder has been renamed from uppercase Teamserver to teamserver
a makefile is not present in the directory, making it impossible to call make
The fix should be pretty simple, just replace Havoc/Teamserver with Havoc/teamserver and replace make with go build.
Also, the dockerfile does not specify an entrypoint, so the readme.md is wrong too, since by executing docker run -it -d -v havoc-c2-data:/data havoc-teamserver it would just start container with /bin/bash.
Did You Do a Pull First?
Latest (You performed a pull first)
Did You Try With the Dev Branch?
Yes (You tried using the dev branch but the problem persist)
Relevant log output
> [4/4] RUN cd Havoc/Teamserver/ && chmod +x ./Install.sh && ./Install.sh && make:
0.620 /bin/sh: 1: cd: can't cd to Havoc/Teamserver/
------
Teamserver-Dockerfile:57
--------------------
55 | #
56 | # Build the cloned repos copy of the Teamserver-Client
57 | >>> RUN cd Havoc/Teamserver/ && chmod +x ./Install.sh && ./Install.sh && make
58 | #
59 | # ------------------------------------------------------------------------------#
--------------------
ERROR: failed to solve: process "/bin/sh -c cd Havoc/Teamserver/ && chmod +x ./Install.sh && ./Install.sh && make" did not complete successfully: exit code: 2
Did You Read Over Your Issue First?
[X] I declare I made an effort and provided the necessary information for replication of the issue.
Contact Details
No response
What happened?
While building the teamserver docker container with
docker build -t havoc-teamserver .
, the user would face errors on line 58 for two major reasons:Teamserver
toteamserver
make
The fix should be pretty simple, just replace
Havoc/Teamserver
withHavoc/teamserver
and replacemake
withgo build
.Also, the dockerfile does not specify an entrypoint, so the readme.md is wrong too, since by executing
docker run -it -d -v havoc-c2-data:/data havoc-teamserver
it would just start container with/bin/bash
.Did You Do a Pull First?
Latest (You performed a pull first)
Did You Try With the Dev Branch?
Yes (You tried using the dev branch but the problem persist)
Relevant log output
Did You Read Over Your Issue First?