papermerge icon indicating copy to clipboard operation
papermerge copied to clipboard

Docker installation stuck at Configuring tzdata

Open AllienWorks opened this issue 5 years ago • 3 comments

In case you experience issues with docker image provided by linuxserver.io/papermerge, please open bug report in their repository.

Description Installation via Docker (docker-compose up in /docker/1.4/) gets stuck on "Configuring tzdata" step.

Expected Installation should finish successfully.

Actual Here's the terminal output where the install gets stuck:

(...)
Setting up tzdata (2020d-0ubuntu0.20.04) ...
debconf: unable to initialize frontend: Dialog
debconf: (TERM is not set, so the dialog frontend is not usable.)
debconf: falling back to frontend: Readline
Configuring tzdata
------------------

Please select the geographic area in which you live. Subsequent configuration
questions will narrow this down by presenting a list of cities, representing
the time zones in which they are located.

  1. Africa      4. Australia  7. Atlantic  10. Pacific  13. Etc
  2. America     5. Arctic     8. Europe    11. SystemV
  3. Antarctica  6. Asia       9. Indian    12. US
Geographic area: 8

After that, nothing happens (I waited around 15 mins).

Info:

  • OS: Docker on Synology NAS
  • Browser: N/A
  • Database: N/A
  • Papermerge Version: latest (https://github.com/ciur/papermerge/commit/c7c835abae8b72d4dbb15c9afa9fa9ac396ba39f)

AllienWorks avatar Nov 25 '20 17:11 AllienWorks

@AllienWorks, thank you for opening this bug.

ciur avatar Nov 27 '20 13:11 ciur

not sure what I can do here. Docker images from docker/1.4/ folder were tested with Ubuntu 20.04.

ciur avatar Nov 30 '20 15:11 ciur

Based on the output:

debconf: unable to initialize frontend: Dialog
debconf: (TERM is not set, so the dialog frontend is not usable.)

I guess dialog is not present, and the fallback readline doesn't read any user input for some reason.. I'd try to add dialog package to installed package before all this.

Either way, it's weird that it works somewhere and fails elsewhere (after all, it's Docker, so I'd imagine it would behave the same on every machine).

AllienWorks avatar Nov 30 '20 15:11 AllienWorks