search

scrapinghub / splash

Lightweight, scriptable browser as a service with an HTTP API
BSD 3-Clause "New" or "Revised" License
4.09k stars 513 forks source link

Docker userns remap breaks builds #948

Closed AngryUbuntuNerd closed 4 years ago

AngryUbuntuNerd commented 5 years ago

When building a Dockerfile with Scrapy base image in a BitBucket pipeline, it now breaks on the first build step (FROM scrapinghub/splash) with this error:

failed to register layer: Error processing tar file(exit status 1): Container ID 834600147 cannot be mapped to a host ID

According to the BitBucket help page this issue is due to the fact that they have enabled userns remapping for security reasons. They also say that some images will not handle this properly, and Scrapy is seemingly one of them.

Until this is fixed, the Scrapy docker image can essentially not be used in BitBucket pipelines, or anywhere that activates this feature.

kmike commented 5 years ago

Do you know what caused this error in Splash Docker image? Is it the use of USER directive? FTR, we had to use non-default (non-root) user in Splash because Chromium doesn't work under root.

AngryUbuntuNerd commented 4 years ago

It seems this issue is now fixed, a rerun of the same pipeline works.