Skip to content

container build jobs produce LegacyKeyValueFormat warnings from docker

When you run a build, the container build jobs produce LegacyKeyValueFormat warnings from docker:

https://gitlab.com/pm215/qemu/-/jobs/11632175953

#13 writing image sha256:a86bcaeb45b51b9612fad91b703b464ddec30ccc8e5314a3ccbf3e3a73e00d4b done
#13 naming to registry.gitlab.com/pm215/qemu/qemu/debian-arm64-cross:latest done
#13 DONE 0.1s
 11 warnings found (use docker --debug to expand):
 - LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format (line 76)
 - LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format (line 77)
 - LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format (line 78)
 - LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format (line 79)
 - LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format (line 181)
 - LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format (line 184)
 - LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format (line 191)
 - LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format (line 180)
 - LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format (line 182)
 - LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format (line 183)
 - LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format (line 75)

If this syntax is deprecated I guess we should switch away from it?

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information