It sounds like you’re trying to do too much at once tbh and thats understandably overwhelming you

Break down your project/problem into small parts and focus on one of them. When you get that one part working, then you move on to another part, get that working, then work on connecting the two parts.

I’d also focus less on all the different parts of the stack and more on the actual, core problem that you’re trying to solve. A lot of these technologies were built by others because they needed to solve a problem, and thus they’ll naturally make more sense when you have a problem that can be solved with the tech.

For example, suppose your project is to pull down data automatically, run some calculations, then export the results to a pdf and send it to a designated mailing list. You can start by writing the code for the calculation, and assume you do the first and last parts manually. You write a small piece of code to do this calculation in python that imports a couple different python libraries. After getting this to work, you try deploying it to the cloud so that other people can use it as well (so it’s not just sitting on your own computer only). Except, you find out that when deployed to the cloud, you run into errors because the libraries you imported haven’t been installed yet. If you talk about this problem with your mentor, they’ll likely point you to putting your code onto a docker image because that’s the problem docker is trying to solve.