Bug fixes for 4.2 release

Dockerfile

@@ -0,0 +1,22 @@
+FROM debian:bookworm-slim
+RUN groupadd -r fpocket && useradd --no-log-init -r -g fpocket fpocket
+RUN apt update -y && apt install -y gcc g++ make libnetcdf-dev && rm -rf /var/lib/apt/lists/*
+
+# all of this mess is essentially to have a minimalistic build at the end
+COPY makefile /opt/fpocket/
+COPY src /opt/fpocket/src
+COPY man /opt/fpocket/man
+COPY headers /opt/fpocket/headers
+COPY obj /opt/fpocket/obj
+COPY scripts /opt/fpocket/scripts
+COPY bin /opt/fpocket/bin
+COPY plugins/LINUXAMD64 /opt/fpocket/plugins/LINUXAMD64
+COPY plugins/include /opt/fpocket/plugins/include
+COPY plugins/noarch /opt/fpocket/plugins/noarch
+
+WORKDIR /opt/fpocket
+
+RUN make && make install && make clean
+USER fpocket
+WORKDIR /tmp
+CMD ["fpocket"]

README.md

@@ -81,10 +81,10 @@ docker build -t fpocket/fpocket .
 This will build fpocket into your local fpocket/fpocket image. You can then run fpocket/mdpocket etc using: 
 
 ```bash
-docker run -v `pwd`:/WORKDIR fpocket/fpocket fpocket -f data/sample/1UYD.pdb
+docker run -v `pwd`:/workdir fpocket/fpocket fpocket -f /workdir/yourfile.pdb
 ```
 
-Here you mount your current directory with your input files into the preconfigured `/WORKDIR` in the docker container and then run fpocket on a file in that mounted folder.
+Here you mount your current directory with your input files into the preconfigured `/workdir` in the docker container and then run fpocket on a file in that mounted folder. Make sure that the folder is writeable to others if you run it through docker.
 
 ### Installing