4/2/2023 0 Comments Running docker on mac m1=> => naming to docker.io/bouke/vcsim-test 0.0s => CACHED COPY -chown=appuser -from=build /temporary-tmp-directory /tmp 0.0s => CACHED COPY -from=build /etc/group /etc/group 0.0s => CACHED COPY -from=build / etc/passwd / etc/passwd 0.0s => CACHED COPY -from=build /etc/ssl/certs/ca-certificates.crt /etc/ssl/certs/ 0.0s => CACHED RUN mkdir /temporary-tmp-directory & chmod 777 /temporary-tmp-directory 0.0s => CACHED RUN adduser -disabled-password -gecos "" -home "/nonexistent" -shell "/sbin/nologin" -no-create-home -uid "10001" "app 0.0s => load metadata for docker.io/library/golang:1.17.5-buster 0.5s => load build definition from Dockerfile.vcsim 0.0s You need JavaScript enabled to view it.2/Dockerfile.vcsim. pkg/mod//vmware/ This email address is being protected from spambots. When building the container you can define which platform it uses for the baseImage.ĭocker run -p 8989:8989 bouke/vcsim-test:latest /vcsim versionīut that doesn't bin % docker build -platform linux/arm64 -t bouke/vcsim-test -f. So in file ' Dockerfile.vcsim' change the 3rd line from: However, the original docker file points to an older go baseImage: golang:1.16.0-buster amd64. So, the next step is to create a docker container, using this binary:ĭocker build -platform linux/arm64 -t bouke/vcsim-test -f. vcsim versionĪlso, when checking the file, I'm getting the correct bin % file vcsim Running it didn't give an issue, but it DOES bin %. So I downloaded the source and compiled it to a binary, which went into the default bin folder of my go path. My first thought was to build the binary from source, compiled on the M1 chip, resulting in a native executable, and put that into a container.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |