For the case of self-compiled Docker image, no Baidu app appears

[CicoZhang]

Hey, there: I compiled the Docker image to evade the issue of the expired software. After deploying the new Docker instance, I did not find BaiduYun inside, Have I mistakenly done something?

Thanks in advance.

[john-shine]

which Dockerfile do you build? BaiduNetdisk app auto launch if right things.

[CicoZhang]

@john-shine I see, it seems that I compiled a wrong Docker file (in the root dir), I should compile the one in the directory BaiduNetdisk, shouldn't I? Thanks for pointing it out. :+1:

[CicoZhang]

I hope this won't affect anything.

--> Finished Dependency Resolution
Error:  Multilib version problems found. This often means that the root
       cause is something else and multilib version checking is just
       pointing out that there is a problem. Eg.:

         1. You have an upgrade for dbus-libs which is missing some
            dependency that another package requires. Yum is trying to
            solve this by installing an older version of dbus-libs of the
            different architecture. If you exclude the bad architecture
            yum will tell you what the root cause is (which package
            requires what). You can try redoing the upgrade with
            --exclude dbus-libs.otherarch ... this should give you an error
            message showing the root cause of the problem.

         2. You have multiple architectures of dbus-libs installed, but
            yum can only see an upgrade for one of those architectures.
            If you don't want/need both architectures anymore then you
            can remove the one with the missing update and everything
            will work.

         3. You have duplicate versions of dbus-libs installed already.
            You can use "yum check" to get yum show these errors.

       ...you can also use --setopt=protected_multilib=false to remove
       this checking, however this is almost never the correct thing to
       do as something else is very likely to go wrong (often causing
       much more problems).

       Protected multilib versions: 1:dbus-libs-1.10.24-7.el7.i686 != 1:dbus-libs-1.6.12-17.el7.x86_64
Error: Protected multilib versions: mesa-dri-drivers-17.2.3-8.20171019.el7.i686 != mesa-dri-drivers-17.0.1-6.20170307.el7.x86_64
Error: Protected multilib versions: openldap-2.4.44-15.el7_5.i686 != openldap-2.4.44-5.el7.x86_64
Error: Protected multilib versions: 1:cups-libs-1.6.3-35.el7.i686 != 1:cups-libs-1.6.3-29.el7.x86_64
The command '/bin/sh -c yum check-update -y ;     yum install -y --setopt=tsflags=nodocs libv4l.i686 fontconfig.i686 libXcomposite.i686 libXinerama.i686 libgphoto2.i686 libxml2.i686 libxslt.i686 openldap.i686 sane-backends-libs.i686 mesa-dri-drivers.i686 isdn4k-utils.i686 gsm.i686 gstreamer-plugins-base.i686 lcms2.i686 mesa-libOSMesa.i686 libtiff.i686 gnutls.i686 glibc.i686 zlib.i686 freetype.i686 libgcc.i686 libXext.i686 alsa-lib.i686 cups-libs.i686 dbus-libs.i686 libXcursor.i686 libXi.i686 libXrandr.i686 libXrender.i686 libXxf86vm.i686 openssl.i686 libpng.i686 libX11.i686 mesa-libGL.i686 freetype.x86_64 glibc.x86_64 libICE.i686 libICE.x86_64 libSM.i686 libSM.x86_64 libX11.x86_64 libXext.x86_64 libgcc.x86_64 libpng.x86_64 nss-mdns.i686 nss-mdns.x86_64 pygtk2 zlib.x86_64 wqy-microhei-fonts &&     yum clean all && rm -rf /var/cache/yum/*' returned a non-zero code: 1

[john-shine]

@john-shine I see, it seems that I compiled a wrong Docker file (in the root dir), I should compile the one in the directory BaiduNetdisk, shouldn't I? Thanks for pointing it out. 👍

Yes, that`s right

&& the build error log can affect crossover to run, better to debug with terminal in docker container. Hard to reproduce this condition, you should do it yourself.