The "Using Jenkins agents3" documentation illustrates how to create anew node (cloud):

In Dashboard > Manage Jenkins > Nodes
, do check you see it listed:

You should now see This node is being launched.
.
If that’s not the case, you can now press the Relaunch agent
button and wait a few seconds. You can now click on the Log
button on the left, then you should receive the message:
Agent successfully connected and online on the last log line.

If your Jenkins controller does not start the agent via ssh, please check the port you configured on your agent. Copy it, and then click on the Advanced…
button. You will then be able to paste the port number into the Port
textfield.
So double-check and try to follow that process, and see if the agent would be available then in your Job definition.
Note: the comments from your video suggests an issue with the image used:
I wasn't able to get jenkins to install python so I couldn't finish the last 2 projects
Same issue but it was the agent, docker agent python, it was messed but ima do another.
The tutorial attempts to replace docker-agent-alpine (in which python3 is not known) by docker-agent-python, which you can see here.
It has a CMD ["/bin/sh"]
: as explained in "Dockerfile CMD
instruction will exit the container just after running it", try and run it to check its log and see if it is because of that CMD it exits immediately.
For example, jenkins/jnlp-agent-python
uses an ENTRYPOINT ["/usr/local/bin/jenkins-agent"]
which seems promising.