Taking inspiration from the example storage project, I created the following script: #!/env/bin bash I think I need the NVMe to be mounted before Postgres is started. Plus, the dynamic udev detection would be started after the container has started. I don’t think I need udev for this, as the documentation seems to indicate that udev is only needed for dynamically mounting and unmounting USB drives and/or additional SD cards. So then, there must be some way to mount an “external” drive, but just once when the container is started, not dynamically while the container is running. The Dockerfile is a recipe for building an image, not a “startup” script. I think the error is caused by the device, /dev/nvme0n1p1, not being available during the build. I get a mount: permission denied (are you root?) error. This does not work, regardless of the base image used.
RUN mount -t ext4 -o rw /dev/nvme0n1p1 /mnt/nvme # FROM balenalib/jetson-xavier-nx-devkit-ubuntu
In my naive understanding, I converted the commands from the SSH session to manually mount the drive to the Dockerfile: # DO NOT FOLLOW THIS DOCKERFILE. Thus, the blkid | grep 'LABEL="nvme"' command is used to get the device name instead of the recommended label-based mounting command. There is no -L option for the mount command in the Alpine base images. Side note, I was initially confused by the Mounting external storage media documentation because it is for the non-Alpine base images despite the example project using an Alpine base image. I recognize that the Balena base images do some additional work for udev and device/hardware access, but regardless of the base/parent image used, I am still having problems. The TimescaleDB source image contains an Alpine distribution, and I have done the above with the balenalib/jetson-xavier-nx-devkit-alpine and balenalib/jetson-xavier-nx-devkit-ubuntu base images, too. At least the NVMe is recognized by the host and I can manually access it from a container. I SSH-ed into the running container, and I manually mounted the NVMe SSD, where I have formatted the NVMe with the ext4 format and given it the nvme label. This successfully builds an image with Postgres/Timescale, but the data will be stored at /var/lib/postgres/data on the SD card, or eMMC depending on the Jetson Xavier NX devkit and device provisioning. # FROM balenalib/jetson-xavier-nx-devkit-alpine I have the following Dockerfile: # FROM balenalib/jetson-xavier-nx-devkit-ubuntu I have BalenaOS and the containers running from the SD Card, but I would like the database to be persisted and stored on the NVMe. var/lib/postgres/data, in my single-container application on my Jetson Xavier NX SD Card devkit.
#Timescaledb postgresql 13 how to#
I am utterly lost on how to use my NVMe SSD for my Postgres data, i.e.
0 kommentar(er)
