Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue while building workspace #1482

Closed
grafikkaos opened this issue Apr 12, 2018 · 5 comments
Closed

Issue while building workspace #1482

grafikkaos opened this issue Apr 12, 2018 · 5 comments
Labels

Comments

@grafikkaos
Copy link

Info:

  • Docker version: 18.03.0-ce, build 0520e24:
  • Laradock commit: 0c41fce:
  • System info : PC:
  • System info disto/version: Windows 10 x64

Issue:

While building workspace, I am getting an error installing libway client


Expected behavior:

Building of workspace should be not be failing.


Reproduce:

In the .env file, enable the installation of laravel dusk packages.


Relevant Code:

WORKSPACE_INSTALL_DUSK_DEPS=true
@dontinhqt
Copy link

dontinhqt commented Apr 17, 2018

I have a problem as such
can not install build worworkingpace when
WORKSPACE_INSTALL_DUSK_DEPS = true

error

E: Failed to fetch http://security.ubuntu.com/ubuntu/pool/main/w/wayland/libwayland-client0_1.12.0-1~ubuntu16.04.2_amd64.deb  404  Not Found [IP: 91.189.88.162 80]

E: Failed to fetch http://security.ubuntu.com/ubuntu/pool/main/w/wayland/libwayland-cursor0_1.12.0-1~ubuntu16.04.2_amd64.deb  404  Not Found [IP: 91.189.88.162 80]

E: Failed to fetch http://security.ubuntu.com/ubuntu/pool/main/w/wayland/libwayland-server0_1.12.0-1~ubuntu16.04.2_amd64.deb  404  Not Found [IP: 91.189.88.162 80]

E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?
ERROR: Service 'workspace' failed to build: The command '/bin/sh -c if [ ${INSTALL_DUSK_DEPS} = true ]; then   apt-get -y install zip wget unzip xdg-utils     libxpm4 libxrender1 libgtk2.0-0 libnss3 libgconf-2-4 xvfb     gtk2-engines-pixbuf xfonts-cyrillic xfonts-100dpi xfonts-75dpi     xfonts-base xfonts-scalable x11-apps   && wget https://dl.google.com/linux/direct/google-chrome-stable_current_amd64.deb   && dpkg -i --force-depends google-chrome-stable_current_amd64.deb   && apt-get -y -f install   && dpkg -i --force-depends google-chrome-stable_current_amd64.deb   && rm google-chrome-stable_current_amd64.deb   && wget https://chromedriver.storage.googleapis.com/${CHROME_DRIVER_VERSION}/chromedriver_linux64.zip   && unzip chromedriver_linux64.zip   && mv chromedriver /usr/local/bin/   && rm chromedriver_linux64.zip ;fi' returned a non-zero code: 100

@Dryr
Copy link
Contributor

Dryr commented Apr 22, 2018

You can fix it by adding apt-get update in the DUSK section of the workspace's Dockerfile

RUN if [ ${INSTALL_DUSK_DEPS} = true ]; then \
  apt-get update \
  && apt-get -y install zip wget unzip xdg-utils \
    libxpm4 libxrender1 libgtk2.0-0 libnss3 libgconf-2-4 xvfb \
    gtk2-engines-pixbuf xfonts-cyrillic xfonts-100dpi xfonts-75dpi \
    xfonts-base xfonts-scalable x11-apps \
  && wget https://dl.google.com/linux/direct/google-chrome-stable_current_amd64.deb \
  && dpkg -i --force-depends google-chrome-stable_current_amd64.deb \
  && apt-get -y -f install \
  && dpkg -i --force-depends google-chrome-stable_current_amd64.deb \
  && rm google-chrome-stable_current_amd64.deb \
  && wget https://chromedriver.storage.googleapis.com/${CHROME_DRIVER_VERSION}/chromedriver_linux64.zip \
  && unzip chromedriver_linux64.zip \
  && mv chromedriver /usr/local/bin/ \
  && rm chromedriver_linux64.zip \
;fi

@johnreitano
Copy link

I had this same problem and "apt-get update -y" fixed the problem. Can someone update the repo with this fix? Thanks!

@stale
Copy link

stale bot commented Feb 2, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the Stale label Feb 2, 2020
@stale
Copy link

stale bot commented Feb 23, 2020

Hi again 👋 we would like to inform you that this issue has been automatically closed 🔒 because it had not recent activity during the stale period. We really really appreciate your contributions, and looking forward for more in the future 🎈.

@stale stale bot closed this as completed Feb 23, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants