bekasoft/derby repository overview

⁠Apache Derby 10.14.2.0

This image is made for ARM v6 and v7, but can be used on other architectures.

Image is based on openjdk:8-jre-alpine.

⁠Running image

Run it providing a local database folder if needed:

$ mkdir -p /var/db-data
$ docker run -d --restart=always -v /var/db-data:/dbstorage -p 1527:1527 --name derby-server bekasoft/derby:10.14.2.0
$ docker logs derby-server

Then server will be available on:

• Port number: 1527
• SSL: off
• Listening to: 0.0.0.0
• Database files: /var/db-data

⁠Creating a sample database

You may use ij tool from within container to do so:

$ docker exec -it derby-server /derby/bin/ij
ij> CONNECT 'jdbc:derby://localhost/testdb;create=true';
ij> CREATE SCHEMA schema_01 AUTHORIZATION dbo_01;
ij> SHOW SCHEMAS;
ij> EXIT;

You may then use DBeaver or other tools to create schemas, tables, and so.

⁠Backup database

You may try this:

$ docker exec -it derby-server /derby/bin/ij
ij> CONNECT 'jdbc:derby://localhost/testdb;create=true';
ij> CALL SYSCS_UTIL.SYSCS_BACKUP_DATABASE('./backup_folder');
ij> EXIT;

⁠Extract DDL from database

You may try this:

$ docker exec -it derby-server /derby/bin/dblook -d 'jdbc:derby://localhost/testdb' -o testdb_ddl.sql

⁠Safely stop server

We need first to stop server inside the container, which automatically stops the container:

$ docker exec -it derby-server /derby/bin/stopNetworkServer
$ docker logs derby-server
$ docker ps -a

Last command shows that derby-server container exited.

⁠Re-run server

No need to reconfigure the container, just start it using:

$ docker container start derby-server