novice question - bug

[andrewufrank]

I read your blog and wanted to try out an example. I selected lynx and started it with

docker run -it \
    --name lynx \
    jess/lynx

and got

Can't Access `file://localhost/usr/share/doc/lynx/lynx_help/about_lynx.html.gz'
Alert!: Unable to access document.

lynx: Can't access startfile 

I guess there is some startup/help file from a regular installation required and not included in the container.
One point more why dockerization for the desktop is a good idea - as you explain. Thank you for the blog!

[issue-label-bot]

Issue-Label Bot is automatically applying the label bug to this issue, with a confidence of 0.67. Please mark this comment with 👍 or 👎 to give our bot feedback!

Links: app homepage, dashboard and code for this bot.

[eoingroat]

The container is based on debian:bullseye-slim. Bullseye is the testing distribution for debian.

The missing file is from lynx-common which hasn't been built / isn't available for bullseye yet (go here, and when you click list of files the error "No such package in this suite on this architecture" appears). If you select the active distribution "buster" you will see the files are there.

Now this is a bit of a pain as the help files are crucial to understanding how to use lynx for someone that hasn't used it before, but for someone who has it probably isn't a problem.

Options:

• build and upstream lynx-common to debian bullseye / prompt the maintainer to do so
  OR
• switch from bullseye to buster
  OR
• wait until its fixed

I've added it as a nice to have to my xmas list to take time to look at building and submitting at some point this holiday, but it is a long list and I've never been involved with debian upstreaming before.