Stef Walter
Stef Walter
You need to use an old build of docker inside of the atomicapp image, built with golang 1.5. The basic point of this bug is that atomicapp images can contain...
> It's most likely just the old image that's being used.. We can direct users to use more up-to-date images in the FAQ if they experience this bug. The point...
Examples of the build problems: ``` /data/src/FBGEMM/src/FbgemmI8Depthwise3DAvx2.cc: In function ‘void fbgemm::depthwise_3d_same_pad_(const conv_param_t&, int32_t, const uint8_t*, const int32_t*, const PackedDepthWiseConvMatrix&, const float*, int32_t, uint8_t*, const int32_t*, const BIAS_TYPE*, const float*, int,...
> @stefwalter seems this is a gcc issue, see #1666 > > > This uninitialized variable issue is being addressed with #1697. However, this alone will not fix the build...
@dwrobel This is a similar patch to #650, and you might choose to bring it into your branch for merging at the same time.
Updated after further tweaks.
I would expect that ```bootc install``` doesn't need to know the registry. What if the image was local, and not pushed to a registry?
Why is this a foot-gun? Why would fetch check be an error? Should it only be a warning by default?