Unable to recover MySQL 5.6 database (InnoDB)

I have tried several different suggestions of other questions here, with no luck …

This is a MySQL database that runs version 5.6.41, which uses the InnoDB engine, and the instance is running out of a Docker image. (https://hub.docker.com/_/mysql?tab=tags&page=1&name=5.6.41) The image has my main database files (ibd and frm files) linked outside the instance.

Here is the error: InnoDB: Error: trying to access page number 0 in space 842,
InnoDB: space name /

InnoDB: which is outside the tablespace bounds.
InnoDB: Byte offset 0, len 16384, i/o type 10.
InnoDB: If you get this error at mysqld startup, please check that
InnoDB: your my.cnf matches the ibdata files that you have in the
InnoDB: MySQL server.
2019-09-12 14:59:26 7f2fe639e700 InnoDB: Assertion failure in thread 139843702744832 in file fil0fil.cc line 5666

I tried to use the innodb_force_recovery flag in all values ​​(including 5-6). The above error occurs when I use the mysql command line tool and login DROP TABLE .

. The main problem is that I can no longer access the database to try any of these recovery options.

This probably started to happen after a host system crash (MacOS 10.13.6) that caused an unexpected shutdown of my Docker container while writing files.

I think my ibdata or ib_logfiles files are corrupt, but I can't find a way to recover the database without cleaning everything and recover it from a mysqldump (which may not even work).

I don't care about the data in this table, I can recover data from a mysql development / test server. I would just like not to go through the trouble of starting everything from scratch.

Here are some other stackex q that I have seen: MySQL cannot delete the table

Trying to resolve the MySQL error "outside the limits of the table space", but the recovery of the table with mysqldump fails

Any suggestions?
(If you need more information, such as the configuration of my variables / my.cnf files or the information of the database structure, ask)