Dear dev team, I am facing an issue while running docker build command on ui docker file. Any idea why it's picking the wrong folder location and how to correct it?
[root@localhost ui]# docker build -t apache/skywalking_ui:latest -f /root/Skywalking/apache-skywalking-apm-7.0.0/docker/ui/Dockerfile.ui . Sending build context to Docker daemon 7.168kB Step 1/12 : FROM XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX 1.8.0_212: Pulling from secure/centos7/java-no-root f34b00c7da20: Already exists eb6fa8aee67b: Pull complete 9bbcc9b518bc: Pull complete 005a0fc85ceb: Pull complete 119b69811fdd: Pull complete 08e8d91ef6a4: Pull complete 774587db1daf: Pull complete aba9d0a26254: Pull complete 1f512ad40247: Pull complete 60cf11c20ca8: Pull complete a3e772fc4871: Pull complete 1d104a6939f0: Pull complete 3b8e9c7cd6df: Pull complete 312ef4a98a12: Pull complete e3822d229a84: Pull complete Digest: sha256:1f3e2412aa4492e0568f785812bdb141bdc8f1b9c1459a936ac9f78a9839b387 Status: Downloaded newer image for XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX ---> b8f357001b9a Step 2/12 : USER root ---> Running in 48032eb1d56a Removing intermediate container 48032eb1d56a ---> 09f7d1f90c5b Step 3/12 : ENV DIST_NAME=apache-skywalking-apm-bin JAVA_OPTS=" -Xms256M " SW_OAP_ADDRESS="127.0.0.1:12800" SW_TIMEOUT="20000" ---> Running in 790c89a4d5d0 Removing intermediate container 790c89a4d5d0 ---> a7c2decec67e Step 4/12 : COPY "$DIST_NAME.tar.gz" / *COPY failed: stat /var/lib/docker/tmp/docker-builder158450567/apache-skywalking-apm-bin.tar.gz: no such file or directory* On Wed, 17 Jun 2020 at 17:51, Gaurav Kodmalwar <gkodmal...@qualys.com> wrote: > Dear team, > > > > Do we have source code for skywalking oap, ui and base? Because our > company doesn't allow external docker pull commands. We build our source > code and then create its image. Finally, convert that into a kubernetes > helm to use it. Can you please share only source code for skywalking and no > docker file? > > > > Thanks, > > Gaurav > > > <https://www.qualys.com/email-banner> > > > > This message may contain confidential and privileged information. If it > has been sent to you in error, please reply to advise the sender of the > error and then immediately delete it. If you are not the intended > recipient, do not read, copy, disclose or otherwise use this message. The > sender disclaims any liability for such unauthorized use. NOTE that all > incoming emails sent to Qualys email accounts will be archived and may be > scanned by us and/or by external service providers to detect and prevent > threats to our systems, investigate illegal or inappropriate behavior, > and/or eliminate unsolicited promotional emails (“spam”). If you have any > concerns about this process, please contact us. >
