tzuhsiao/baidunetdisk-docker

Docker化的百度云盘官方Linux客户端+VNC服务器 (Dockerized Baidu Netdisk official Linux client with VNC server)

运行

docker run --name baidunetdisk \
  -v {配置文件夹}:/root/baidunetdisk \
  -v {下载文件夹}:/root/baidunetdiskdownload \
  -p {VNC端口}:5900 \
  -p {WEB端口}:6080 \
  -e VNC_SERVER_PASSWD='{VNC密码}' \
  tzuhsiao/baidunetdisk:latest

通过VNC访问

默认端口为5900，使用任何VNC客户端连接，如VNC® Viewer，TightVNC。

通过浏览器访问

默认端口为6080。

baidunetdisk-docker's Issues

有没有办法去掉i3最下面的状态栏

我尝试了注释掉了 i3status，实时状态消失了，但是还有空间占用，以及最左侧的一个数字

bar {
        # status_command i3status
}

小白求教，有没有试过在群晖的系统下可以用吗，我试了但是连接VNC后黑屏，网页打开是一个列表，用里面的vnc.html链接进去也是黑屏，如下图

VNC进去黑屏
https://gitee.com/xiaominglei001/forMarkdown/blob/master/%E6%8D%95%E8%8E%B78.PNG

网页打开是一个列表，用里面的vnc.html链接进去登陆后也是黑屏
https://gitee.com/xiaominglei001/forMarkdown/blob/master/%E6%8D%95%E8%8E%B79.PNG

nginx反向代理，默认是文件浏览模式

期望能给改成默认vnc.html

VNC server failed

您好，
我在运行时发现错误，表现是连不到VNC服务
经查发现错误日志包含如下内容，日志显示上一次正确运行是 6/28/2021

07/07/2021 14:56:29 -usepw: found /root/.vnc/passwd
07/07/2021 14:56:29 x11vnc version: 0.9.13 lastmod: 2011-08-10 pid: 385
07/07/2021 14:56:29 XOpenDisplay(":1") failed.
07/07/2021 14:56:29 Trying again with XAUTHLOCALHOSTNAME=localhost ...

07/07/2021 14:56:29 ***************************************
07/07/2021 14:56:29 *** XOpenDisplay failed (:1)

*** x11vnc was unable to open the X DISPLAY: ":1", it cannot continue.
*** There may be "Xlib:" error messages above with details about the failure.

Some tips and guidelines:

** An X server (the one you wish to view) must be running before x11vnc is
started: x11vnc does not start the X server. (however, see the -create
option if that is what you really want).

** You must use -display , -OR- set and export your $DISPLAY
environment variable to refer to the display of the desired X server.

• Usually the display is simply ":0" (in fact x11vnc uses this if you forget
  to specify it), but in some multi-user situations it could be ":1", ":2",
  or even ":137". Ask your administrator or a guru if you are having
  difficulty determining what your X DISPLAY is.

** Next, you need to have sufficient permissions (Xauthority)
to connect to the X DISPLAY. Here are some Tips:

• Often, you just need to run x11vnc as the user logged into the X session.
  So make sure to be that user when you type x11vnc.
• Being root is usually not enough because the incorrect MIT-MAGIC-COOKIE
  file may be accessed. The cookie file contains the secret key that
  allows x11vnc to connect to the desired X DISPLAY.
• You can explicitly indicate which MIT-MAGIC-COOKIE file should be used
  by the -auth option, e.g.:
  x11vnc -auth /home/someuser/.Xauthority -display :0
  x11vnc -auth /tmp/.gdmzndVlR -display :0
  you must have read permission for the auth file.
  See also '-auth guess' and '-findauth' discussed below.

** If NO ONE is logged into an X session yet, but there is a greeter login
program like "gdm", "kdm", "xdm", or "dtlogin" running, you will need
to find and use the raw display manager MIT-MAGIC-COOKIE file.
Some examples for various display managers:

 gdm:     -auth /var/gdm/:0.Xauth
          -auth /var/lib/gdm/:0.Xauth
 kdm:     -auth /var/lib/kdm/A:0-crWk72
          -auth /var/run/xauth/A:0-crWk72
 xdm:     -auth /var/lib/xdm/authdir/authfiles/A:0-XQvaJk
 dtlogin: -auth /var/dt/A:0-UgaaXa

Sometimes the command "ps wwwwaux | grep auth" can reveal the file location.

Starting with x11vnc 0.9.9 you can have it try to guess by using:

          -auth guess

(see also the x11vnc -findauth option.)

Only root will have read permission for the file, and so x11vnc must be run
as root (or copy it). The random characters in the filenames will of course
change and the directory the cookie file resides in is system dependent.

See also: http://www.karlrunge.com/x11vnc/faq.html
root@baidunetdisk:/var/log#

The Vnc showing the black screen when docker running and able to input the password

Hi, hope you doing well.

The pull and run in the docker successfully , but can not working after in put the vnc password. just showing the black screen,
can you please guide me how to fix it?
and the log didn't showing anything.
the log and screenshot are all attached, please check

Thanks
Peter

ARM的CPU不支持

入标题所示，目前镜像不支持ARM的cpu，希望作者大大以后支持！！！