serde_yaml v0.8.11 issues in v0.2.0 of kubernix

[afreakk]

I was getting this when running sudo kubernix

[DEBUG] Kubeconfig created for kube-scheduler
[DEBUG] Creating kubeconfig for admin
[DEBUG] Kubeconfig created for admin
[DEBUG] No previous run file '/home/afreak/temp/kubernix/kubernix-run/etcd/run.yml' found, writing new one
[⠈  1m] ███████░░░░░░░░░░░░░░░░░░  8/28 Starting etcd
thread '<unnamed>' panicked at 'attempted to leave type `linked_hash_map::Node<yaml_rust::yaml::Yaml, yaml_rust::yaml::Yaml>` uninitialized, which is invalid', /build/rustc-1.48.0-src/library/core/src/mem/mod.rs:658:9
stack backtrace:
   0: rust_begin_unwind
   1: core::panicking::panic_fmt
   2: core::panicking::panic
   3: linked_hash_map::LinkedHashMap<K,V,S>::insert
   4: <serde_yaml::ser::SerializeStruct as serde::ser::SerializeStruct>::serialize_field
   5: kubernix::process::_IMPL_SERIALIZE_FOR_Run::<impl serde::ser::Serialize for kubernix::process::Run>::serialize
   6: serde_yaml::ser::to_string
   7: kubernix::process::Process::start
   8: kubernix::container::Container::start
...

but when i ran cargo update -p serde_yaml and updated from 0.8.11 to 0.8.16 the error dissapeared.

Maybe we could have a 0.2.1 with 0.8.16 of serde_yaml, but weird i am the first one to experience that issue. I am using nixos btw.