[Docker] Docker images don't work due > The usage of relative paths for mountpoints will now produce a warning (librunc)

[cortiz]

Describe the bug

Due to opencontainers/runc#2917 and opencontainers/runc#3004 docker/runc
in some Docker environments creating or running a Crafter image fails, this issue was fixed on runc 1.0.0 that was released today, but until that is rollout with the OS package management tools the issue will persist (Redhat 8, Ubuntu 20.04LTS)
Also on the Release notes of runc

Deprecations:
The usage of relative paths for mountpoints will now produce a warning
(such configurations are outside of the spec, and in future runc will
produce an error when given such configurations). (#2917, #3004)

Adding full mount points will also future-proof the current docker images.

Regards

[avasquez614]

@cortiz is this issue the same as this one? #4759.

[cortiz]

@avasquez614 Yes

[sumerjabri]

Fixed in 3.1.15

[phuongnq]

@cortiz The issue is fixed in 3.1.15. Does the fix work for you?

[russdanner]

@phuongnq please confirm in 4.x and close

[phuongnq]

Confirmed with version

Docker version 20.10.11, build dea9396

Run the following command is fine:

docker-compose down && docker-compose up