The shell script working on a cron, with all the packages I now have installed on the system, and with some distributed configuration items… I made a Docker Image with the little stuff I have.<\/p>\n\n\n\n
FROM ubuntu:latest\nRUN apt-get update \\\n\t&& apt-get install -y ocrmypdf \\\n\t&& apt-get install tesseract-ocr-deu \\\n\t&& apt-get install -y imagemagick \\\n\t&& apt-get install -y cron\nRUN groupadd -g 1001 scanner \\\n && useradd -rm -d \/home\/scanner -s \/bin\/bash -g 1001 -u 1001 scanner\nWORKDIR \/home\/scanner\nCOPY --chown=scanner:scanner . .\nVOLUME \/home\/scanner\/archive\nVOLUME \/home\/scanner\/scanner\nRUN crontab -l | { cat; echo \"* * * * * timeout 1h flock -n \/home\/scanner\/apps\/lock\/translateNewFiles.lock su scanner -c \/home\/scanner\/apps\/scripts\/translateNewFiles.sh\"; } | crontab -\nCMD [\"cron\", \"-f\"]\n\n<\/code><\/pre>\n\n\n\nBehold, the Dockerfile. It would have worked out of the box, but… there is of course on thing in there that is not okay, the user management. I want to really have a “scanner” user on the system which writes all the files of our project. After a lot of failed attempts, the cron is running as root in the container and the translateNewfiles.sh is executed with the scanner user, where at the moment the user is hardcoded in uid and gid matching the outside user. I should change that.<\/p>\n\n\n\n
The data store is on the outside, just directories mounted in.<\/p>\n\n\n\n
version: \"3.3\"\nservices:\n dochauser:\n build: .\n volumes:\n - \/home\/scanner\/dochauser_mount\/archive:\/home\/scanner\/archive\n - \/home\/scanner\/dochauser_mount\/scanner:\/home\/scanner\/scanner<\/code><\/pre>\n\n\n\nWhich means the docker-compose.yml looks like this and is quite simple for my tests.<\/p>\n\n\n\n
This will not be the nicest Docker Image ever created, but it works for me for the moment.<\/p>\n\n\n\n
Oh shit, why do I get an access denied error trying to stop my own container?<\/p>– All Ubuntu Server LTS users ever? <\/cite><\/blockquote>\n\n\n\ni don’t know if this is common, but I had to remove docker-compose and docker and snap and apparmor and install everything freshly via apt-get. Now the system feels stable. But I had a bit of hate for this basic workflow not to go properly for me in Ubuntu Linux.<\/p>\n","protected":false},"excerpt":{"rendered":"
The shell script working on a cron, with all the packages I now have installed on the system, and with some distributed configuration items… I made a Docker Image with the little stuff I have. Behold, the Dockerfile. It would have worked out of the box, but… there is of course on thing in there …<\/p>\n