You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The container we're publishing is a bit of a misnomer. Its tpm2software/tpm2-tss but the tss isn't in that container.
No it was just a name... I never intended it to mean that.
I'd argue the container images in this repo should really be tpm2-base. Since it's the base image required to compile the tss.
I can see that argument...
We should then have Dockerfiles in each other repo which provide built versions of those projects respectively named.
Which build, latest release, master, etc? The containers are really intended just for the CI or near ready to go sandboxes for playing in.
Renaming gets fun, because things then all need to be updated in all the other projects that use these for the CI pipeline. As much as I like where your head is on this, I don't think renaming them really adds that much value.
The container we're publishing is a bit of a misnomer. Its tpm2software/tpm2-tss but the tss isn't in that container.
I'd argue the container images in this repo should really be tpm2-base. Since it's the base image required to compile the tss.
We should then have Dockerfiles in each other repo which provide built versions of those projects respectively named.
The text was updated successfully, but these errors were encountered: