Does LittleDict show too much about the implementation?

[PallHaraldsson]

I noticed:

julia> x = LittleDict{String, Int}()
LittleDict{String, Int64, Vector{String}, Vector{Int64}}()

should it show similar to other Dicts:

LittleDict{String, Int64}()

I also noticed for a recursive one:

julia> x = LittleDict{LittleDict, Int}()
LittleDict{LittleDict, Int64, Vector{LittleDict}, Vector{Int64}}()

julia> x
LittleDict{LittleDict, Int64, Vector{LittleDict}, Vector{Int64}} with 1 entry:
  LittleDict{LittleDict, Int64, Vector{LittleDict}, Vector{Int64}}(#= circular reference @-1 =#) => 0

this "circular reference" is not shown for other dicts (I'm not saying it's untrue). I just noticed this compared to: #65.

[antoineco]

The culprit was actually simple to find. Shims must follow the naming convention io.containerd.*:

https://github.com/containerd/nerdctl/blob/2eeffe086961098f2e040f784c1707a1adc1cdb4/pkg/cmd/container/run_runtime.go#L41-L43

[yankay]

HI @antoineco

When I try to investigate the issue and run with docker.

root@kay200:~# docker container create --runtime com.example.sample.v1 docker.m.daocloud.io/nginx:alpine
Error response from daemon: Unknown runtime specified com.example.sample.v1

So Does the expected result need to be the same with docker :-)

[antoineco]

I guess that's fine for me. If shims for containerd need to follow a certain naming convention I'll follow that convention.

[AkihiroSuda]

This is still a bug

[zhangguanzhang]

any update?