Docker desktop for windows 2.3.0.3 breaks MariaDB alter table again

[Daemach]

The problem mentioned in #5604 is happening now in 2.3.0.3. I am using a bound volume. Alter table to add columns crashes with this error:

Error on rename of './coldbox/#sql-alter-1-b' to './coldbox/users' (errno: 16 "Device or resource busy")

[mat007]

Could you tell us a bit more about how you run this? A compose file maybe?

[Daemach]

version: '3.6' # if no version is specificed then v1 is assumed. Recommend v2 minimum volumes: sql-data: networks: IPCDNet: services: mysql: image: mariadb:10.5 container_name: ipcd_dbase environment: MYSQL_ROOT_PASSWORD: '2h2=he2+E' volumes: - type: bind source: ./data target: /var/lib/mysql # - type: bind # source: ./database/backups # target: /var/opt/mssql/backups ports: - 3306:3306 networks: - IPCDNet restart: always adminer: image: adminer:latest restart: always ports: - 8080:8080 networks: - IPCDNet

[Daemach]

Can I get you more information on this? I'm about to give up on docker and just install it locally. Every time I try to add or rename a column the database has to be dropped and recreated.

[Daemach]

Error on rename of './coldbox/#sql-alter-1-44' to './coldbox/users' (errno: 16 "Device or resource busy")

[mat007]

Running compose with the compose file you provided seems to be working fine for me, do I need to do something else to trigger the issue?

[Daemach]

Renaming columns or tables triggers it, but it's semi-random.

[L1yp]

My docker works the same way on wsl2., docker cp cannot manipulate files in containers.

For example:

docker cp nginx.conf nginx-web:/etc/nginx/nginx.conf
> Error response from daemon: Error processing tar file (exit status 1): unlinkat / etc/nginx/nginx.conf: device or resource busy
docker exec -it nginx-web rm -f /etc/nginx/nginx.conf
> rm: cannot remove '/etc/nginx/nginx.conf': Device or resource busy

[docker-robott]

Issues go stale after 90 days of inactivity.
Mark the issue as fresh with /remove-lifecycle stale comment.
Stale issues will be closed after an additional 30 days of inactivity.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle stale

[docker-robott]

Closed issues are locked after 30 days of inactivity.
This helps our team focus on active issues.

If you have found a problem that seems similar to this, please open a new issue.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle locked