This looks very much like a reference mismatch. Your CRAM header will have M5 tags, so it's best to find references that way than trying to force it to use a specific reference file (and potentially getting it wrong). It's good that it calls this out too, otherwise you'd just decode and get the wrong data back.
Check the samtools.1 man page and search for REF_PATH and REF_CACHE environment variables. If you have them unset and have an internet connection it'll automatically download them from EBI and cache them. If not, you can prepopulate it by downloading them yourself and pointing REF_PATH to that directory structure, or using the samtools/misc/seq_cache_populate.pl script on the (correct!) reference to generate the MD5 files.
Note this is also both a faster way of driving CRAM because it doesn't need any newline / uppercasing on the fasta file as it reads the CRAM, permitting mmap usage, but it also is safer as it's immune to strangeness of Chr1 vs chr1 vs 1 shenanigans.
what is the output of
and the output of
samtools view -H 6026111_23153_0_0.cram | grep '^@SQ' | grep -w chr1
@SQ SN:chr1 LN:248956422 M5:6aef897c3d6ff0c78aff06ac189178dd UR:/home/dnanexus/./GRCh38_full_analysis_set_plus_decoy_hla/GRCh38_full_analysis_set_plus_decoy_hla.fa
and
grep -w chr1 ~/GRCh38_full_analysis_set_plus_decoy_hla.fa.fai
chr1 1829166 112 70 71
this is NOT the same reference.
In your BAM header the length of chr1 is 248956422
while in the fasta file the length of chr 1 is 1829166