Run the base image and vim does not display properly

[singlaive]

It might be weird why I run the base image jare/alpine-vim rather than the vim-bundle image. I do so in order to learn how to create my own vim docker image from scratch and attempted to use the base image as a starting point.

I only need add one line before ENTRYPOINT statment of alpine-vim-base/Dockerfile:
WORKDIR /workspace

Build this image after I cd into the repo:
docker build -t docker-vim alpine-vim-base

And I run it for editing:
docker run -it --rm -v pwd:/workspace docker-vim alpine-vim-base/Dockerfile

Surprisingly, vim does not render all content. You can see 1/3 of lines are blank:

And if I run :set nu to display line number, the problem becomes more visible, and you can not even scroll up to go to the begining of the file:

I must say this issue is intermittent, and one out of ten it might give me proper display. Please anyone can help me?
Environment: macOS Mojave 10.14.1
Docker:

[JAremko]

@singlaive But if you build vim-bundle it works fine? I haven't re-built the images for a while. Mb it's a new issue with next vim/deps versions.

[singlaive]

Yes vim-bundle is fine. I am not saying there is anything wrong with your Dockerfile or your repo, I think it is some pitfall about run vim in docker. The symptom is:

• Building vim-bundle ends up with solarised scheme not installed properly somehow. when run vim-bundle, it throw error about not finding solarised, then entering vim it displays fine. BUTTTTTT, if I explicitly update the Dockerfile for vim-bundle and install solarised theme thus no error, it does not display properly exactly like what presented above.
• Shrinking the Dockerfile of alpine-vim to be only those four lines and it still reproduces this issue:
  From alpine
  apk add vim
  WORKDIR /workspace
  ENTRYPOINT vim
  Note: Actually no matter you install vim from apk or build it from source there is no difference, the issue exists.
• If you do docker run -it --entrypoint /bin/sh to get into the container first, then run vim inside, it displays fine.

It does look like it is a configureation issue only appearing when you run vim via docker, but I tried quite a few hours and cannot narrow down the root cause. Please help.

[JAremko]

@singlaive You can try running it via mosh. See https://github.com/JAremko/drop-in

It should help if it's some kind of terminal compatibility problem.

[JAremko]

@singlaive Also try setting env variable TERM=xterm or mb TERM=xterm-256color via docker's -e run-flag.