mhalbritter
commented
8 months ago I've edited your comment to improve the formatting. You might want to check out this Mastering Markdown guide for future reference.
Closed Vetal2001 closed 8 months ago
mhalbritter
commented
8 months ago I've edited your comment to improve the formatting. You might want to check out this Mastering Markdown guide for future reference.
Vetal2001
commented
8 months ago I've edited your comment to improve the formatting. You might want to check out this Mastering Markdown guide for future reference.
Thank you. I'm just starting to use github
wilkinsona
commented
8 months ago @Vetal2001 can you confirm the version of Docker that you're using and whether or not you're customising the buildpacks? The issue that you commented on before was about a problem that's specific to Docker 25.0 with custom buildpacks. In the title of this issue you've said that you're using Docker 24.0 and you don't appear to be customising the buildpacks.
Vetal2001
commented
8 months ago @Vetal2001 can you confirm the version of Docker that you're using and whether or not you're customising the buildpacks? The issue that you commented on before was about a problem that's specific to Docker 25.0 with custom buildpacks. In the title of this issue you've said that you're using Docker 24.0 and you don't appear to be customising the buildpacks.
I've tried with different versions 25 and 24. I don't ustomising the buildpacks
wilkinsona
commented
8 months ago The URL that's being used for the pull looks to be correct to me so I suspect it may be a problem with your Docker installation or its configuration. Can you please share the complete output from running each of the following two commands on the command line:
docker context inspectdocker pull paketobuildpacks/builder-jammy-base:latestVetal2001
commented
8 months ago
- docker context inspect
Thanks for your reply
PS C:\projects\serv-mirep-microservices\fm-loading-telematics-data-service> &$env:ProgramFiles\Docker\docker context inspect
[
{
"Name": "default",
"Metadata": {},
"Endpoints": {
"docker": {
"Host": "npipe:////./pipe/docker_engine",
"SkipTLSVerify": false
}
},
"TLSMaterial": {},
"Storage": {
"MetadataPath": "\u003cIN MEMORY\u003e",
"TLSPath": "\u003cIN MEMORY\u003e"
}
}
]
PS C:\projects\serv-mirep-microservices\fm-loading-telematics-data-service> &$env:ProgramFiles\Docker\docker pull paketobuildpacks/builder-jammy-base:latest
latest: Pulling from paketobuildpacks/builder-jammy-base
image operating system "linux" cannot be used on this platform: operating system is not supported
scottfrederick
commented
8 months ago image operating system "linux" cannot be used on this platform: operating system is not supported
As Andy suggested, this appears to be a problem with the configuration of your local Docker. Can you try some of the solutions in this StackOverflow post: https://stackoverflow.com/questions/50786984/docker-image-operating-system-linux-cannot-be-used-on-this-platform-while?
I'm getting a build error. I have attached a file with the full log and pom file full log.txt pom.txt