Restore MySQL dump to a container fails with ERROR 1114 "The table is full"
&quot;Table is full&quot; implies a disk space problem.  But there are other issues:
How much RAM in your container?
tmp_table_size=2G
max_heap_table_size=2G

not more than 1% of RAM available.  Anyway, those are used during complex SELECTs; they are not used during INSERTs.

dump of size around 18GB

Depending on the datatypes, etc, etc, the amount of disk needed could be a lot less or a lot more than 18GB.  I would be skeptical about 30GB being enough.  The dump is text; the data may be something else.  For example, a 4-byte INT could take 2 bytes (&quot;0,&quot;) in the dump or 12 bytes (&quot;-1234567900,&quot;) in the dump.  After loading into the database it is likely to take 8-12 bytes, depending on overhead.  That might be a 6x expansion (2-&gt;12) or a shrinkage (12-&gt;8).  (That's just one example.)
If you have integers arbitrarily in BIGINT, that 4 bytes becomes 8.  Shrinking the datatypes (where appropriate) will shrink the disk space needed.  Please provide SHOW CREATE TABLE; there may be some other obvious suggestions.
And what is &quot;overlay&quot;?  It really looks like it hit a limit of 5GB.