Just looked more into this on my end and here is the info...
This check was patched to not be needed on supported systems. It landed in commit revision
399361. However, due to some lag in committing it didn't land in time for V51 which was built at commit rev
382149. So you need to manually use
--disable-setuid-sandbox until the v52 app image lands which should have the proper fix for kernel sandbox support in it.
Do NOT use
--no-sandbox, that disables all security sandboxing which will leave you open to attack. Use
--disable-setuid-sandbox until v52 lands with the fix internally.