The documentation of this image on DockerHub mentions that it uses an 'in memory backend'. However, I tested it locally and noticed that the catalog was in fact persisted (i.e. it still existed after rebooting the container). I assume this is due to an error in the source code.
I think the connection string jdbc:sqlite:file:/tmp/iceberg_rest_mode=memory in
needs to be replaced. Currently, this creates an iceberg_rest_mode=memory file in the tmp directory of the container that is persisted and is just a regular sqlite DB file.
The documentation of this image on DockerHub mentions that it uses an 'in memory backend'. However, I tested it locally and noticed that the catalog was in fact persisted (i.e. it still existed after rebooting the container). I assume this is due to an error in the source code.
I think the connection string
jdbc:sqlite:file:/tmp/iceberg_rest_mode=memory
inneeds to be replaced. Currently, this creates an
iceberg_rest_mode=memory
file in thetmp
directory of the container that is persisted and is just a regularsqlite
DB file.