Closed brunodbo closed 5 years ago
As mentioned on https://github.com/romaricp/kit-starter-symfony-4-docker/issues/10, running rm -rf /var/lib/apt/lists/*
before doing apt update
does seem to be a workaround. Still wondering why this error happens in the first place. Could it be some caching issue somewhere?
Hi @brunodbo! I have no idea of why you may be experiencing such issue. I have gone through things like that though while I was under a VPN but here you say that this is running at GitLab CI so that may not be related. Is it still happening? Did you figure out anything else?
@juampynr Thanks for your reply! Unfortunately, I haven't been able to figure out more details about this issue. I also posted about it in GitLab's support tracker (https://gitlab.com/gitlab-com/support-forum/issues/4528#note_177733868), with one other person commenting they experienced the same issue.
In any case, it seems like this isn't related to the drupal8ci image, so closing this.
I started getting an error when running
apt-get update -y
in GitLab CI, using thedrupal8ci
image. I'm wondering if anyone else is seeing this, since it seems unrelated to GitLab (someone else was able reproduce the error when pulling the image from Docker directly):Any idea what could be causing this to start happening all of a sudden? My GitLab CI had been working fine for months. I've tried clearing the runner caches, but no luck.