Closed Kr0ff closed 2 years ago
looks like a temporari issue with the repo, nothing wrong with the container configs. it seems like it is working as expected now
Thanks i will test and come back with results
I've done some testing and it keeps breaking on random packages. That said the issue is not related to the container, but I reported it mainly so the devs are aware of this (not that much can be done...).
Im closing the issue now. Thanks !
i am adding and apt configuration flag to retry a failed download 4 times before giving up. give me a moment to build, test and commit it
I am trying to build a custom Dockerfile for a Parrotsec docker container to support desktop access.
It seems that using certain packages such as parrot-pico, parrot-tools-common, parrot-tools and other similar meta-packages cause certain domains to return a "404 Not Found" for the needed dependency packages.
Prior to fetching the meta-packages I mentioned above, I am running:
with the belief that this would prevent APT from getting those annoying 404 errors.
This essentially breaks the build of the container and there isn't really a workaround I believe but could be wrong.
I would recommend collecting all packages for meta-packages and hosting them on just one domain e.g https://deb.parrot.sh/parrot/
That way maintainers will be able to easily update and track old packages and update faster.
Example of what I'm getting as an error from APT