2 answers
If you're working in a team where backend developers or DevOps use Docker, then yeah - you should at least understand the basics so you can spin up the whole stack locally and not catch bugs because of environment differences. But if your setup is simple and the frontend is completely separate, you can get by without it - though Docker definitely won't hurt your resume.
Docker isn't something you need because you're a frontend developer, but because modern projects often require running several services at once - a database, a backend, maybe a cache. If you want to work locally properly without the "it works on my machine" problem, learn the basics: what a container is, how to read docker-compose, how to recreate your environment. You don't need to dive deep into DevOps, but understanding what's happening when you spin up a container saves you hours of debugging.
Your answer
Log into answer.