Mysql service image crashes upon use

Build Environment
1

Hello!

We are testing out CircleCi as a possible replacement for our Jenkins build server.
I am therefore trying to get one of our services up and running on CircleCi.

But we have the problem that MySQL crashes when our tests try to use it.
We are running the standard free version using docker.

In the config.yml the setup looks like this.

    docker:
      - image: cimg/openjdk:14.0.1
      - image: mysql:5.6.30
        environment:
          MYSQL_ROOT_PASSWORD: password
          MYSQL_DATABASE: database
          MYSQL_USER: username
          MYSQL_PASSWORD: password
      - image: rabbitmq:3.8.9
        environment:
          RABBITMQ_NODENAME: our-node-name
      - image: redis:2.8

The error I get from mysql is this:

MySQL init process done. Ready for start up.

2021-04-16 13:11:16 0 [Note] mysqld (mysqld 5.6.30) starting as process 8 ...
2021-04-16 13:11:16 8 [Note] Plugin 'FEDERATED' is disabled.
2021-04-16 13:11:16 8 [Note] InnoDB: Using atomics to ref count buffer pool pages
2021-04-16 13:11:16 8 [Note] InnoDB: The InnoDB memory heap is disabled
2021-04-16 13:11:16 8 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2021-04-16 13:11:16 8 [Note] InnoDB: Memory barrier is not used
2021-04-16 13:11:16 8 [Note] InnoDB: Compressed tables use zlib 1.2.8
2021-04-16 13:11:16 8 [Note] InnoDB: Using Linux native AIO
2021-04-16 13:11:16 8 [Note] InnoDB: Using CPU crc32 instructions
2021-04-16 13:11:16 8 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2021-04-16 13:11:16 8 [Note] InnoDB: Completed initialization of buffer pool
2021-04-16 13:11:16 8 [Note] InnoDB: Highest supported file format is Barracuda.
2021-04-16 13:11:16 8 [Note] InnoDB: 128 rollback segment(s) are active.
2021-04-16 13:11:16 8 [Note] InnoDB: Waiting for purge to start
2021-04-16 13:11:16 8 [Note] InnoDB: 5.6.30 started; log sequence number 1625997
2021-04-16 13:11:16 8 [Note] Server hostname (bind-address): '*'; port: 3306
2021-04-16 13:11:16 8 [Note] IPv6 is available.
2021-04-16 13:11:16 8 [Note]   - '::' resolves to '::';
2021-04-16 13:11:16 8 [Note] Server socket created on IP: '::'.
2021-04-16 13:11:16 8 [Warning] 'proxies_priv' entry '@ root@bc9844929986' ignored in --skip-name-resolve mode.
2021-04-16 13:11:16 8 [Note] Event Scheduler: Loaded 0 events
2021-04-16 13:11:16 8 [Note] mysqld: ready for connections.
Version: '5.6.30'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  MySQL Community Server (GPL)
2021-04-16 13:18:12 7fabc73d47002021-04-16 13:18:12 8 [ERROR] InnoDB: Failure of system call pwrite(). Operating system error number is 12.
InnoDB: Error number 12 means 'Cannot allocate memory'.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html
2021-04-16 13:18:12 8 [ERROR] mysqld: The table 'tableName' is full

We do not try to create a lot of data. When I create the data locally the table sizes are around 6 MB.

What are we doing wrong? Do I have to specify that I want any diskspace at all for my mysql-container?
(Another one of our services are using postgres and that is working fine)