Laurent Goderre

I wouldn't be surprised. I think the lesson here is that 300mb is just too low for latest cassandra to run.

I wonder if this Cassandra setting could be the cause: https://cassandra.apache.org/doc/stable/cassandra/configuration/cass_yaml_file.html#native_transport_allow_older_protocols

You could use an init container to achieve this step. You could have the default cassandra container running as the db and another cassandra with an custom entrypoint that runs...

You might be able to implement a custom queue like this one: https://github.com/aws/aws-sdk-rails/blob/main/lib/active_job/queue_adapters/amazon_sqs_adapter.rb

You can run ``` docker exec -u postgres -it postgres psql psql (16.2 (Debian 16.2-1.pgdg120+2)) Type "help" for help. postgres=# \du List of roles Role name | Attributes -----------+------------------------------------------------------------ postgres...

@tomera-cyera I believe `postgres` in this case refers to the OS user which is `postgres` not the db role.

OOh you mean at initialization?

The following works on alpine: ``` echo "version" | nc -vn -w 1 127.0.0.1 11211 ``` Source: https://book.hacktricks.xyz/network-services-pentesting/11211-memcache

And the following works on debian: ``` echo "version" | (exec 3/dev/tcp/localhost/11211; cat >&3; cat

Absolutely! That would be awesome!