Failed to register layer error creating overlay mount to - Исправление ошибок и поиск оптимальных решений проблем

As requested, I’m creating another issue for this error.

Some relevant links that go even more in depth on it, in previous posts (in mo particular order):

version 2.2.0.0: Error while creating mount source path ‘/host_mnt/c/code’: mkdir /host_mnt/c/code: file exists #5516 (comment)
version 2.2.0.0: Error while creating mount source path ‘/host_mnt/c/code’: mkdir /host_mnt/c/code: file exists #5516 (comment)
version 2.2.0.0: Error while creating mount source path ‘/host_mnt/c/code’: mkdir /host_mnt/c/code: file exists #5516 (comment)
docker: Error response from daemon: error creating overlay mount to /var/lib/docker/overlay2/<string-of numbers>fb-init/merged: too many levels of symbolic links. phpmyadmin/docker#267

An additional aside:
In the above link I mention/show that the docker run php:apache container is one of them that also gives this error; it seems after the latest Docker update, it no longer does; however, the docker run wordpress:apache does still give the same overlay error.

I have tried with the latest version of my channel (Stable or Edge)
I have uploaded Diagnostics
Diagnostics ID: 2ECBE1F4-ADE2-4D97-8082-505598CFAE53/20200213120818

Expected behavior

No overlay error while trying to create certain containers. (Apparently not happening to all containers, as I can run many others, though I haven’t picked out a pattern yet).

Actual behavior

Getting an overlay error.

Information

See below

Windows Version: See below
Docker Desktop Version: See below
Are you running inside a virtualized Windows e.g. on a cloud server or on a mac VM: It’s running in Docker Desktop (Hyper-V)

Unfortunately for me, I still have the same issue with an overlay error (which I don’t really understand).

I just installed:

Using this Compose (I left out the MySQL service, to focus on the problem container):

version: '2'

services:

  phpmyadmin:
    container_name: phpmyadmin
    image: 'phpmyadmin/phpmyadmin:latest'
    restart: unless-stopped
    environment:
      - TZ='America/Chicago'
      - "PMA_HOST=mysql"
      - "MYSQL_ROOT_PASSWORD=RlL1#2Z%^W"
      - "PMA_ABSOLUTE_URI=https://my.domain.rocks:3112/phpmyadmin/"
    volumes:
      - "/f/Sites/Web/.config/PHPMyAdmin/Files:/Files:rw,shared"    
      - "/f/Sites/Web/.config/PHPMyAdmin/config.user.inc.php:/etc/phpmyadmin/config.user.inc.php"
      - "/f/Sites/Web/.config/PHPMyAdmin/apache2.conf:/etc/apache2/apache2.conf"
      - "/f/Sites/Web/.config/PHPMyAdmin/Themes/:/var/www/html/themes/"
    depends_on:
      - mysql
    networks:
      - odb

networks:
  odb:
    external:
      name: my-db

Gives me this error (which is the same is the previous Docker Edge version):

{«message»:»Status: failed to register layer: error creating overlay mount to /var/lib/docker/overlay2/a54d40ac5df89eb2c2c9737db85772fe5782ea47c693ceba2eb1889ec2d7f25e/merged: too many levels of symbolic links, Code: 1″,»details»:»Status: failed to register layer: error creating overlay mount to /var/lib/docker/overlay2/a54d40ac5df89eb2c2c9737db85772fe5782ea47c693ceba2eb1889ec2d7f25e/merged: too many levels of symbolic links, Code: 1″}

For what it might also be worth, since I don’t know if the 2 are related in any way, but I’m just throwing it out there, I also get this error when trying to create an Adminer container, and mount a local CSS file to the container:

{«message»:»Error response from daemon: error while creating mount source path ‘/c/Servers/Docker/Containers/Adminer/pepa-linha-dark/adminer.css’: mkdir /c/Servers/Docker/Containers/Adminer/pepa-linha-dark/adminer.css: file exists»,»details»:»Error response from daemon: error while creating mount source path ‘/c/Servers/Docker/Containers/Adminer/pepa-linha-dark/adminer.css’: mkdir /c/Servers/Docker/Containers/Adminer/pepa-linha-dark/adminer.css: file exists»}

I’m running on Win 10 x64 (Version 10.0.18363.657])

Источник

We are facing one issue related to the IoT Edge Module pull in one of the hardware. The Gateway cannot pull all the edge modules as per the deployment manifest file. While downloading some modules, we see the error below in the IoT Edge runtime logs.

Could not pull image XXXXXX/YYYY:6.0.0-amd64

<4>2022-03-28T08:56:44Z [WARN] - 
caused by failed to register layer: 
error creating overlay mount to var/lib/docker/overlay2/24593016a6b6bf0eaf6543d5ec82d94244d5fcb6d25e3be62ed0da70761daacd/merged: 
too many levels of symbolic links

IoT Edge runtime version: 1.1.6

What’s the cause for this error and how to recover from it when the devices are installed at sites during production?

We are not expecting any errors while IoT Edge modules are being pulled as per the deployment manifest file. All the modules should be pulled and running.

Christian

4,2114 gold badges24 silver badges42 bronze badges

asked Apr 4, 2022 at 20:53

See below for my resolution; not sure if this will work for you.

Specifications

Hardware: Jetson Nano
O/S: Ubuntu 18.04
Package: nvidia-jetpack
Version: 4.6-b199
Architecture: arm64
Iotedge version: 1.2
Iotedge Agent: 1.1.12.53348281

Background

I am experiencing the same issue on one (1) of our IoTEdge modules that is running a custom base image. I have checked the base image and it is valid and has not been updated. Also, this same Image/Module is running without issue on 13 other almost identical devices. Overall running nine modules on these machines (includes edgeAgent & edgeHub).

When I inspect the edgeAgent Logs I see the following errors:

Could not create module EnergyCalc
Apr 11 10:31:37 agl-a-f2-h2-u001 aziot-edged[32020]: 2022-04-11T14:31:37Z [WARN] -         caused by: error creating overlay mount to /var/lib/docker/overlay2/8c5855e126f9b652d63bf02f293b2382767077eacb00490bd754db0d0c4085c7-init/merged: no such file or directory

This device did experience a «disk» full scenario. This issue was resolved and then I have uninstalled/reinstalled IoTEdge several times without resolution. Created/Deployed a new image (EnergyCalc2) of the same module on a test machine-works perfectly—however when I deploy to this machine, same problem exists.

Brute force method

Stopped/Removed IoTEdge, Moby-cli, Moby-Engine
Deleted /var/lib/docker directory:
```
rm -r /var/lib/docker
```
Re-installed Moby-Engine, IoTEdge

I would venture there is something in the docker configuration that is causing the problem; I did not had a chance to investigate fully.

Jeremy Caney

6,82354 gold badges48 silver badges74 bronze badges

answered Apr 11, 2022 at 15:14

Delete /var/lib/docker
```
sudo rm -r /var/lib/docker
```
Install the specific Docker version from the apt-cache policy docker-ce candidate list:
```
apt-cache madison docker-ce
```

Choose the version and insert it in the code below:

sudo apt-get install docker-ce=<VERSION_STRING> docker-ce-cli=<VERSION_STRING> containerd.io docker-compose-plugin

Install docker again

Jeremy Caney

6,82354 gold badges48 silver badges74 bronze badges

answered Aug 16, 2022 at 1:11

Источник

Содержание

docker: Error response from daemon: error creating overlay mount to /var/lib/docker/overlay2/ fb-init/merged: too many levels of symbolic links. #267
Comments
Can’t download docker image: failed to register layer #725
Comments
Steps to Reproduce
Expected Behaviour
Observed Behaviour
Context
Technical Info
[Bug]: php-fpm:7.3-work-0.139 not pullable -> failed to register layer error creating overlay mount about devilbox HOT 12 CLOSED
Comments (12)
Related Issues (20)
Recommend Projects
React
Vue.js
Typescript
TensorFlow
Django
Laravel
Recommend Topics
javascript
server
Machine learning
Visualization
Recommend Org
Facebook
Microsoft
error creating overlay mount to . /merged: invalid argument. #2340
Comments
Container Linux Version
Environment
Expected Behavior
Actual Behavior
Reproduction Steps
Other Information
Addon installation broken #3354
Comments
Describe the issue you are experiencing
What is the used version of the Supervisor?
What type of installation are you running?
Which operating system are you running on?
What is the version of your installed operating system?
What version of Home Assistant Core is installed?
Steps to reproduce the issue
Anything in the Supervisor logs that might be useful for us?
Additional information

docker: Error response from daemon: error creating overlay mount to /var/lib/docker/overlay2/ fb-init/merged: too many levels of symbolic links. #267

I’m trying to run this command:

But I keep getting the error:

docker: Error response from daemon: error creating overlay mount to /var/lib/docker/overlay2/[string-of-numbers]-init/merged: too many levels of symbolic links.

The text was updated successfully, but these errors were encountered:

@STaRDoGG no idea, the issue is out of the scope of phpMyAdmin

But my advice would be to remove arguments from the command line until the error is not here.
You will then have found the error in your config 🙂

Thanks for looking into this, guys.

I’m still wrestling with this issue:

I’m even getting it when I remove all volume mounts. i.e. just running:

I only get this issue when trying to run the PHPMyAdmin container.

I am not sure this issue is for phpMyAdmin
Could you try to run the hello world image using the same command ?

@J0WI what do you think about this issue ?

Never heard about it. Is this Windows only?

Could you try to run the hello world image using the same command ?

The hello world image or the ubuntu base image are not comparable. Maybe you can try with wordpress:apache or php:apache ?

@J0WI AHA! You’ve hit on something. (But I’m not experienced enough w/docker yet to know what, lol).

Yes, I am running Docker Desktop in Win 10 x64, running Linux containers.

We can’t help you here, I suggest that you try moving this issue to https://github.com/docker/for-win or https://github.com/docker-library/php 😕

@J0WI ok, thanks. Any ideas though? It seems like you sort of have an idea, based on the suggestion you gave that pointed right to it.

Источник

Can’t download docker image: failed to register layer #725

Steps to Reproduce

run docker pull sharelatex/sharelatex in bash
wait for download

Expected Behaviour

Successfully download the image.

Observed Behaviour

Can’t pull image, due to this error:

Context

Technical Info

I tried prune the image and redownload, but it doesn’t help.

The text was updated successfully, but these errors were encountered:

Seems you have a problem with docker in your system. From the message, it looks like a file system issue. Does it happen pulling images other than sharelatex/sharelatex ?

Seems you have a problem with docker in your system. From the message, it looks like a file system issue. Does it happen pulling images other than sharelatex/sharelatex ?

@mserranom No, it doesn’t happen when pulling other images. But this problem seems to be a docker machine problem, all the images should be the same. If it’s the problem of the image, how come I can’t download but other can?

It looks like you are already running in some type of container. You may want to look into bumping the limit of symbolic links — not sure where that would be, but that’s not something we have a direct influence on. We use many layers, so maybe look in the overlayfs area for a config option to tweak the number of lowerdir s. Good luck!

Источник

[Bug]: php-fpm:7.3-work-0.139 not pullable -> failed to register layer error creating overlay mount about devilbox HOT 12 CLOSED

I thought it could have been related to the image because I experienced it only on the php7.3 image, but what you suggest seems the right thing to focus on. I’ll dig deeper and report as I have more news.
Thanks @cytopia

cytopia commented on January 17, 2023 1

Still, is it possibile to docker-compose up php specifying 0.134 image version instead of the latest 0.139? Thanks!

masiorama commented on January 17, 2023 1

I am gonna try this and keep you posted! Thanks @cytopia!

masiorama commented on January 17, 2023 1

Just a note for the future: since I wanted to upgrade the php image version I decided to dig a bit deeper again.
None of the standard docker commands worked and I was able to fix only with a drastic move: delete /var/lib/docker .
It is worth mentioning that all images and data will completely disappear so it is a good idea to backup your data (databases for example), but at least now I can work with the latest images.

cytopia commented on January 17, 2023

For me this image pulls just fine:

Can you try the docker pull command manually