Can you exec into the container and check the logs under /var/log/mariadb/columnstore and see what is reported. Start at err.log and then go down to debug.log which has the most info. The logs will usually have a more descriptive error as in some cases we can't surface the more specific error due to the way this is implemented.

For a real workload server you might want to map that dir to a volume so you preserve logs across container restarts.

Here is the content of err.log

Oct 10 09:33:49 bfa8440cfce4 cpimport.bin[107674]: 49.773186 |0|0|0| E 34 CAL0087: BulkLoad Error: Actual error row count(1) exceeds the max error rows(0) allowed for table db_name.table_name
Oct 10 09:33:49 bfa8440cfce4 cpimport.bin[107674]: 49.773408 |0|0|0| E 34 CAL0087: BulkLoad Error: Bulkload Read (thread 0) Failed for Table db_name.table_name. Terminating this job.
Oct 10 09:33:49 bfa8440cfce4 writeengineserver[1096]: 49.801613 |0|0|0| E 32 CAL0000: pushing data : PIPE error .........Broken pipe
Oct 10 09:33:51 bfa8440cfce4 writeengineserver[1096]: 51.433036 |0|0|0| E 32 CAL0000: 6336 : cpimport exit on failure (signal -1)
Oct 10 09:33:51 bfa8440cfce4 writeenginesplit[107633]: 51.433331 |0|0|0| E 33 CAL0000: #033[0;31mReceived a Cpimport Failure from PM1#033[0m
Oct 10 09:33:51 bfa8440cfce4 writeenginesplit[107633]: 51.433484 |0|0|0| E 33 CAL0087: BulkLoad Error: #033[0;31mReceived a Cpimport Failure from PM1#033[0m
Oct 10 09:33:51 bfa8440cfce4 writeenginesplit[107633]: 51.433821 |0|0|0| E 33 CAL0000: PM1 : Bulkload Read (thread 0) Failed for Table db_name.table_name. Terminating this job.
Oct 10 09:33:51 bfa8440cfce4 writeenginesplit[107633]: 51.433887 |0|0|0| E 33 CAL0087: BulkLoad Error: PM1 : Bulkload Read (thread 0) Failed for Table db_name.table_name. Terminating this job.

This looks like the kind of error we would see if there is UTF-8 or non-latin1 characters in the data. Is this possible in your case?

By the way i dont know how to put europe timezone into this container since nor dpkg-reconfigure neither apt update seems to be available. (logs are two hours early).
_
Here what i did for that_ https://chrisjean.com/change-timezone-in-centos/

original is ENGINE=InnoDB DEFAULT_CHARSET=utf8 ROW_FORMAT=REDUNDANT

target is Engine=ColumnStore DEFAULT_CHARSET=utf8 and ROW_FORMAT was deleted because it's not supported.

I deleted a lot of keys but if special characters are present it is by mistake.

For memories:

CREATE TABLE `ma_table` ( `ma_table_id` int(11) NOT NULL, `label` text NOT NULL ) ENGINE=ColumnStore DEFAULT CHARSET=utf8;

MariaDB [target]> insert into ma_table select * from source.ma_table;
ERROR 1815 (HY000): Internal error: PM1 : Bulkload Read (thread 0) Failed for Table target.ma_table. Terminating this job.

drop table ma_table.
CREATE TABLE `ma_table` (
-> `ma_table_id` int(11) NULL,
-> `label` varchar(255) NULL
-> ) ENGINE=ColumnStore DEFAULT CHARSET=utf8;

insert into ma_table select * from source.ma_table;
Query OK, 14 rows affected (1.65 sec)
Records: 14 Duplicates: 0 Warnings: 0

One more exemple:

MariaDB [target]> CREATE TABLE `ma_table` (
-> `a` int(11) DEFAULT NULL,
-> `b` int(11) DEFAULT NULL,
-> `c` int(11) DEFAULT NULL,
-> `d` int(11) DEFAULT NULL,
-> `e` varchar(255) DEFAULT NULL,
-> `f` int(255) DEFAULT NULL,
-> `g` datetime DEFAULT NULL,
-> `h` datetime DEFAULT NULL,
-> `i` datetime DEFAULT NULL,
-> `j` varchar(255) DEFAULT NULL,
-> `k` varchar(255) DEFAULT NULL,
-> `l` longtext DEFAULT NULL,
-> `m` longtext DEFAULT NULL
-> ) ENGINE=Columnstore DEFAULT CHARSET=utf8;

MariaDB [target]> insert into ma_table select a,b,c,d,e,f,g,h,i,j,k,l,m from source.ma_table;
ERROR 1030 (HY000): Got error -1 "Internal error < 0 (Not system error)" from storage engine Columnstore

MariaDB [target]> CREATE TABLE `ma_table` (
-> `a` int(11) DEFAULT NULL,
-> `b` int(11) DEFAULT NULL,
-> `c` int(11) DEFAULT NULL,
-> `d` int(11) DEFAULT NULL,
-> `e` varchar(255) DEFAULT NULL,
-> `f` int(255) DEFAULT NULL,
-> `g` datetime DEFAULT NULL,
-> `h` datetime DEFAULT NULL,
-> `i` datetime DEFAULT NULL,
-> `j` varchar(255) DEFAULT NULL,
-> `k` varchar(255) DEFAULT NULL
-> ) ENGINE=Columnstore DEFAULT CHARSET=utf8;

MariaDB [target]> insert into ma_table select a,b,c,d,e,f,g,h,i,j,k from source.ma_table;
Query OK, 2225502 rows affected (16.13 sec)
Records: 2225502 Duplicates: 0 Warnings: 0

So if a columns is a problem (text empty or special char) i must drop it ?

so, to be clear. The original problem you are reporting is that you have two extra TEXT based columns on the destination table?

But i don't understand why it is a problem.

do you have test data and source/destination schemas you can provide us to reproduce the problem?