No OSI- or FSF-approved software license allows you to restrict commercial use. There are some Creative Commons licenses with Non-Commercial clauses, but they are not suitable for software (no warrantee clauses).
So, yes, if that is a strict requirement of yours you will need to dual-license (I assume you mean pick a copyleft license and then dual-license).
Additionally, you will need to get contributors to sign a CLA giving you copyright of their contributions, so that you can relicense the whole codebase.
This will most likely reduce your potential pool of contributors: some won't contribute for philosophical reasons, and there is simply a bigger barrier to entry.
One alternative is to skip the dual-licensing and just use a copyleft license (GPL-v3.0-or-later or AGPL-v3.0-or-later). While these licenses allow commercial use, most companies wouldn't useavoid them because the requirement to release source code isn't compatible with their business model.
(Obviously the few companies that do have compatible business models would be able to profit from your work. However, they could do this anyway if you dual-license. They are likely to be warmer to a regular copyleft rather than dual-license, you will have access to any changes they distribute, and they will most likely contribute those changes to you directly.)