如何在Docker容器中访问显示设备？帧缓冲程序运行异常求助

Hey there, let's get that square executable running in your Ubuntu Docker container. That error you're hitting—Error: cannot open framebuffer device: No such file or directory—is just Docker being safe by default: it doesn't share host hardware devices like /dev/fb0 with containers unless you explicitly tell it to. Here's how to fix it step by step:

1. Mount the Framebuffer Device When Starting the Container #

The simplest fix is to pass the host's /dev/fb0 device into the container when you run it. Use this command instead of a basic docker run:

docker run --device=/dev/fb0 -it your-image-tag /bin/bash

This makes the host's framebuffer device available inside the container, so your square program can find /dev/fb0 just like it did on your VM.

2. Check Permissions (If Needed) #

Most of the time, using the default root user in your Ubuntu 14.04 container will give you access to /dev/fb0 right away. But if you still get permission errors, check the group ownership of /dev/fb0 on your host (it's usually the video group). Then inside the container, add your user to that group:

usermod -aG video your-username

Since you're using root by default, this might not be necessary, but it's good to keep in mind if you switch to a non-root user later.

3. Tweak Your Dockerfile (Optional Cleanup) #

Your current Dockerfile works, but you can make it a bit cleaner and more efficient:

FROM ubuntu:14.04
MAINTAINER xxaxaxax
# Combine apt commands to reduce image layers
RUN apt-get update && apt-get install -y vim gcc
RUN mkdir /home/test
# Set default working directory so you don't have to cd every time
WORKDIR /home/test
ADD hello .
ADD square .

Using && chains the apt-get commands to avoid extra image layers, and WORKDIR sets /home/test as your default directory when you enter the container.

4. Test It Out #

Start the container with the --device flag, navigate to /home/test (or just stay there if you added WORKDIR), and run ./square. It should now access the framebuffer and draw your square without issues.

Bonus: If You Still Hit Snags #

If your host is running an X11 display server, sometimes framebuffer access can be restricted. As a last resort (use this carefully, since it gives the container full host access), you can run the container with the --privileged flag:

docker run --privileged -it your-image-tag /bin/bash

But stick with the --device flag first—it's the more secure option.

内容的提问来源于stack exchange，提问作者Sreejin K