[+] Building 5.2s (7/16) => [internal] load build definition from Dockerfile 0.0s => => transferring dockerfile: 32B 0.0s => [internal] load .dockerignore 0.0s => => transferring context: 2B 0.0s => [internal] load metadata for docker.io/library/ubuntu:20.04 4.4s => [ 1/12] FROM docker.io/library/ubuntu:20.04@sha256:35ab2bf57814e9ff49e365efd5a5935b6915eede5c7f8581e9e1b85e0eecbe16 0.0s => [internal] load build context 0.0s => => transferring context: 7.33kB 0.0s => CACHED [ 2/12] RUN apt-get -qq update -y && apt-get -y -qq install curl wget gnupg host nginx mysql-server php-fpm php-pdo php-mysql php-curl php- 0.0s => ERROR [ 3/12] RUN wget -q -O - https://dl-ssl.google.com/linux/linux_signing_key.pub | apt-key add - 0.7s

[ 3/12] RUN wget -q -O - https://dl-ssl.google.com/linux/linux_signing_key.pub | apt-key add -: #6 0.390 Warning: apt-key output should not be parsed (stdout is not a terminal) #6 0.707 gpg: no valid OpenPGP data found.

executor failed running [/bin/sh -c wget -q -O - https://dl-ssl.google.com/linux/linux_signing_key.pub | apt-key add -]: exit code: 2

I encountered an issue with the CSRF lab while on tryhackme. I was not able to log in with either of the 2 acceptable username and password combinations: admin/admin or ben/ben.

My login is not successful because the cookie token is not being set even when using correct login credentials. This is because the SameSite=none attribute is set, which requires the Secure attribute to be set. The Secure attribute has to be run over an encrypted connection or else it will not be set. Neither the THM machine nor local machines have an encrypted connection, so it seems safe and beneficial to remove them.

To everyone having this problem when trying to run the container on Windows 10, before building, you should replace CRLF Windows carriage return by Unix type LF

1. Open notepad++ and select View -> Show Symbol -> Show End of Line

2. Ctrl+H and replace all Windows CRLF with Unix LF. Do not forget to select Extended search mode.

3. Save, build and run it again. You should now see landing page correctly.

Happy hacking and love.