text:
Convert model

I built sherpa-ncnn with MINGW (Windows) and all work good and i get well results.
wav filename: 1089-134686-0001.wav
wav duration (s): 6.625
Started!
Done!
Recognition result for 1089-134686-0001.wav
text:  AFTER EARLY NIGHTFALL THE YELLOW LAMPS WOULD LIGHT UP HERE AND THERE THE SQUALID QUARTER OF THE BRAFFLES
timestamps: 0.32 0.92 1 1.12 1.4 1.56 1.6 1.76 1.96 2.08 2.2 2.24 2.4 2.52 2.56 2.64 2.8 3 3.24 3.48 3.6 3.72 3.92 4.36 4.48 4.52 4.76 4.84 5 5.04 5.16 5.2 5.44
 5.6 5.8 5.84 5.96 6.04 6.24
Elapsed seconds: 2.155 s
Real time factor (RTF): 2.155 / 6.625 = 0.325

But i cant find anywhere some converter (or converter.py) for original whisper models to NCNN model.
For example if i want inference "medium" multi-language model from whisper.

sherpa-ncnn does not support whisper models.
https://github.com/k2-fsa/sherpa-onnx supports whisper. Its usage is very similar to  that of sherpa-ncnn.
You can find converted whisper models for sherpa-onnx at
https://k2-fsa.github.io/sherpa/onnx/pretrained_models/whisper/index.html

Also i tested small model on Orange Pi ..
It's good. thank You for your work,
root@orangepi2:~/software/sherpa-ncnn/build# ./bin/sherpa-ncnn-microphone
ALSA lib pcm.c:2666:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.front
ALSA lib pcm.c:2666:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.rear
ALSA lib pcm.c:2666:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.center_lfe
ALSA lib pcm.c:2666:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.side
Num devices: 5
Use default device: 3
Name: default
Max input channels: 128
Started
0: all right rich price thank you so much fur taken the time to
join us here is there anything else that you want to add before
i let you go

authors: csukuangfj magicse


text:
vits-melo-tts-zh_en 模型疑问

当中文中遇到长段的英文时会明显出现性能下降，这可能是什么问题？这个模型有优化方案吗？这似乎是目前唯一的中英文混合模型，但是英文发音并不好，很多单词不会发音，看起来和 cum 字典有关

是否可以降低输出采样率以减少字节拷贝？

中文模型，日期读的不对，这个怎么解决呀

请贴运行参数，或者，去看文档

source: gharchive/issue

authors: chenmj201601 csukuangfj endink

license_type: permissive

license_source: github-api


text:
Test and validate mysql 8.x

Test mysql 8.x and formally add support.

@davidnuzik Hi, Could you tell me is there a completion date?

Hi @linyinli there is no date. This item is in the backlog to be picked up later when we review items in the backlog. I cannot provide a date at this time. We do have an interest to test this though, if we have some time free up in a couple of months we may take this on then. It's possible we may be able to validate by the end of the year (no promises).

Unfortunately Digital Ocean Managed MySQL DBs only support MySQL version 8.0. I'd like to use DO Managed MySQL, but k3s apparently doesn't support it yet?

It should work fine. It's tested upstream by kine, just QA hasn't signed off on it yet.
https://github.com/k3s-io/kine/blob/master/scripts/test-run-mysql#L25-L32

Yup, I tested it out on DO and it works fine with 1.24 RC

Closing because this appears to be resolved

authors: brandond caroline-suse-rancher davidnuzik linyinli pcgeek86


text:
Setup ip6 masquarading rules if for local subnets

When the IPv6 CIDR is in the unique local address range setup ipv6
masquarading, otherwise assume the ipv6 network is globally routed.
Signed-off-by: Sjoerd Simons sjoerd@collabora.com

Proposed Changes
Currently when configure a dual-stack cluster it seems somewhat assumed that the cluster cidr is a public range otherwise the pods don't have ipv6 internet connectivity. Adjust it so that when the cluster cidr is not public the pods get masquarading for ipv6 as well similar to what happens for ipv4
Types of Changes
bugfix
Verification
Setup a dual-stacked cluster with a private ipv6 range (e.g. fd00::/56) and try to access public ipv6 service from a pod
Linked Issues
fixes #4683
User-Facing Change

Dual-stacked clusters using a private ipv6 range will now automatically have ipv6 masquarding available

Further Comments
This  requires  flannel-io/flannel#1513

I think we need to make this configurable. If someone has deployed private ipv6 addressing across their entire environment as well as within their clusters, they may actually desire the current behavior.

I think we need to make this configurable. If someone has deployed private ipv6 addressing across their entire environment as well as within their clusters, they may actually desire the current behavior.

If they do i would expect them to have a globally addressable subnet :) But sure i can look into that. Though imho the behaviour  the behaviour proposed in this patch should probably be the default as apart from the very special cases as you mention here it should just work.
Fwiw the same rationale would ofcourse also work for ipv4 where k3s just always masquarades

I don't know a ton about how people actually deploy private ipv6 networks, but my understanding is that some folks prefer to do all their NAT at the edge so that they retain visibility into client addresses on firewalls and such.

Could you make create the PR in Flannel instead of k3s? I think it makes more sense there

I think we need to make this configurable. If someone has deployed private ipv6 addressing across their entire environment as well as within their clusters, they may actually desire the current behavior.

If they do i would expect them to have a globally addressable subnet :) But sure i can look into that. Though imho the behaviour the behaviour proposed in this patch should probably be the default as apart from the very special cases as you mention here it should just work.
Fwiw the same rationale would ofcourse also work for ipv4 where k3s just always masquarades

In ipv4 there is a flag that configures this behaviour

I think we need to make this configurable. If someone has deployed private ipv6 addressing across their entire environment as well as within their clusters, they may actually desire the current behavior.

If they do i would expect them to have a globally addressable subnet :) But sure i can look into that. Though imho the behaviour the behaviour proposed in this patch should probably be the default as apart from the very special cases as you mention here it should just work.
Fwiw the same rationale would ofcourse also work for ipv4 where k3s just always masquarades

In ipv4 there is a flag that configures this behaviour

I'm probably dense; but could you point me to that so i can copy the logic :) ; From what i can tell from:
https://github.com/k3s-io/k3s/blob/d71b3358714711c2f95bc6cc6020320b6f6e5f0f/pkg/agent/flannel/flannel.go#L71
k3s always does masq on ipv4? While the flannel standalone binary  seems to have an single ipMasq flag which either applies masquarading rules on both ipvv4 and ipv6 if enabled.

Could you make create the PR in Flannel instead of k3s? I think it makes more sense there. I can review it there and we can release a new version as soon as it is ready

Sure i can do something in flannel as well (never played with it standalone tbh).  Could you let me know what behaviour you'd like to see with flannel (also auto-detect? with seperation of the masq flags for v4/v6 there?)

Could you make create the PR in Flannel instead of k3s? I think it makes more sense there. I can review it there and we can release a new version as soon as it is ready

Sure i can do something in flannel as well (never played with it standalone tbh). Could you let me know what behaviour you'd like to see with flannel (also auto-detect? with seperation of the masq flags for v4/v6 there?)

Sorry, I have just realized that I was wrong. Flannel upstream executes this feature in the main.go file, which is a file we are not consuming in k3s. The code should be in k3s (in flannel.go, as you PR does). Therefore, ignore my comment before, you don't have to contribute to flannel and sorry for confusing you.
I'd prefer to have that parameter configurable. It might be that the user has a big network using private ip addresses (e.g. in the range of 10.0.0.0/8) and routing directly to pods (no NAT) is something required. Besides, the current implementation of the flannel binary, only accepts FLANNEL_IPMASQ, i.e. there isn't one for ipv4 and one for ipv6. Therefore, we should apply masquerade in both or in none.
Currently in k3s we are applying masquerade always: https://github.com/k3s-io/k3s/blob/master/pkg/agent/flannel/flannel.go#L72 and we always set FLANNEL_IPMASQ to true: https://github.com/k3s-io/k3s/blob/master/pkg/agent/flannel/flannel.go#L74.
I suggest adding a new flag in k3s (e.g. --flannel-ipmasq) that contains a boolean and defaults true. If true, we apply the iptables masquerade rules in the forward chain. If false, we don't. The value is also passed to the function WriteSubnetFile to generate the correct /var/run/flannel/subnet.env with FLANNEL_IPMASQ

I think we need to make this configurable. If someone has deployed private ipv6 addressing across their entire environment as well as within their clusters, they may actually desire the current behavior.

If they do i would expect them to have a globally addressable subnet :) But sure i can look into that. Though imho the behaviour the behaviour proposed in this patch should probably be the default as apart from the very special cases as you mention here it should just work.
Fwiw the same rationale would ofcourse also work for ipv4 where k3s just always masquarades

In ipv4 there is a flag that configures this behaviour

I'm probably dense; but could you point me to that so i can copy the logic :) ; From what i can tell from:
https://github.com/k3s-io/k3s/blob/d71b3358714711c2f95bc6cc6020320b6f6e5f0f/pkg/agent/flannel/flannel.go#L71
k3s always does masq on ipv4? While the flannel standalone binary seems to have an single ipMasq flag which either applies masquarading rules on both ipvv4 and ipv6 if enabled.

Sorry, I was mixing flannel and k3s code :facepalm:

Could you make create the PR in Flannel instead of k3s? I think it makes more sense there. I can review it there and we can release a new version as soon as it is ready

Sure i can do something in flannel as well (never played with it standalone tbh). Could you let me know what behaviour you'd like to see with flannel (also auto-detect? with seperation of the masq flags for v4/v6 there?)

Sorry, I have just realized that I was wrong. Flannel upstream executes this feature in the main.go file, which is a file we are not consuming in k3s. The code should be in k3s (in flannel.go, as you PR does). Therefore, ignore my comment before, you don't have to contribute to flannel and sorry for confusing you.
I'd prefer to have that parameter configurable. It might be that the user has a big network using private ip addresses (e.g. in the range of 10.0.0.0/8) and routing directly to pods (no NAT) is something required. Besides, the current implementation of the flannel binary, only accepts FLANNEL_IPMASQ, i.e. there isn't one for ipv4 and one for ipv6. Therefore, we should apply masquerade in both or in none.

This is an area i'm not familiar with; is the subnet env file meant so you can mix stand-lone flannel with k3s? (afaict k3s doesn't read it).
Your suggestion mostly makes sense to me; Apart from treating both v4 and v6 the same especially wrt. Nat. non-natted ipv6 with natted ipv4 (which is what k3s currently does) seems a quite reasonable setup.. I guess if flannel interop is required then i guess it's back to patch flannel first to support differnet policies for both and then follow back up with k3s again ? :)

This is an area i'm not familiar with; is the subnet env file meant so you can mix stand-lone flannel with k3s? (afaict k3s doesn't read it).

stand-alone flannel generates the flannel subnet env file. k3s does it too :) https://github.com/k3s-io/k3s/blob/master/pkg/agent/flannel/flannel.go#L127-L157.
That file contains the config for the flannel binary. The flannel binary receives calls from Kubelet via de CNI API to create the correct veths, or remove them, etc... i.e. create the correct network for the pod

Your suggestion mostly makes sense to me; Apart from treating both v4 and v6 the same especially wrt. Nat. non-natted ipv6 with natted ipv4 (which is what k3s currently does) seems a quite reasonable setup.. I guess if flannel interop is required then i guess it's back to patch flannel first to support differnet policies for both and then follow back up with k3s again ? :)

Yes, if we want to have different policies for both, we would need to change upstream flannel

@sjoerdsimons Can I somehow help you to push this forward? Currently this is preventing me from progressing with my home-production setup and I would really love to be able to use my private IPv6 subnet. :)

Yes, if we want to have different policies for ipv4 and ipv6, we would need to change upstream flannel (or ignore doing masq in ipv6 as it happens right now ;) )

MR for flannel: https://github.com/flannel-io/flannel/pull/1523

This is implemented by https://github.com/k3s-io/k3s/pull/4952. The flag to activate it is --flannel-ipv6-masq and will be out in the next release of k3s (in 1.21, 1.22 and master). Please test it and give us feedback! :)

Yes, if we want to have different policies for ipv4 and ipv6, we would need to change upstream flannel (or ignore doing masq in ipv6 as it happens right now ;) )

MR for flannel: flannel-io/flannel#1523

Replied in your flannel PR. Your implementation is good but it requires the Flannel binary to incorporate those changes too. And consequently, the CNI Bridge too

Yes, if we want to have different policies for ipv4 and ipv6, we would need to change upstream flannel (or ignore doing masq in ipv6 as it happens right now ;) )

MR for flannel: flannel-io/flannel#1523

Replied in your flannel PR. Your implementation is good but it requires the Flannel binary to incorporate those changes too. And consequently, the CNI Bridge too

What thread did i pull; That said i'm a bit surprised this gets closed now based upon our discussion it seems you wanted flannel to get support for multiple policies first (which is why i put in the effort in the first place). But ah well...  Happy to see the functionality gets in one way or the other

Yes, if we want to have different policies for ipv4 and ipv6, we would need to change upstream flannel (or ignore doing masq in ipv6 as it happens right now ;) )

MR for flannel: flannel-io/flannel#1523

Replied in your flannel PR. Your implementation is good but it requires the Flannel binary to incorporate those changes too. And consequently, the CNI Bridge too

What thread did i pull; That said i'm a bit surprised this gets closed now based upon our discussion it seems you wanted flannel to get support for multiple policies first (which is why i put in the effort in the first place). But ah well... Happy to see the functionality gets in one way or the other

Sorry for the confusion and wasting your time. I learnt a few things on the way that changed my opinion. For example, the variable FLANNEL_IPMASQ=true is confusing because it means "don't do IPMASQ on ipv4 and ipv6 because it's already done". I thought it meant the opposite and I thought that was the only way to create masquerading. Therefore, we are leaving that variable as true and do the masquerade ourselves

source: gharchive/pull-request

authors: SchoolGuy brandond manuelbuil sjoerdsimons


text:
[release-1.22] Backport bugfixes and enhancements from master

Proposed Changes
Backport bugfixes and enhancements from master to release-1.22

https://github.com/k3s-io/k3s/pull/5205
https://github.com/k3s-io/k3s/pull/5437
https://github.com/k3s-io/k3s/pull/5464
https://github.com/k3s-io/k3s/pull/5462
https://github.com/k3s-io/k3s/pull/5519
https://github.com/k3s-io/k3s/pull/5207
https://github.com/k3s-io/k3s/pull/5487
https://github.com/k3s-io/k3s/pull/5518
https://github.com/k3s-io/k3s/pull/5382
https://github.com/k3s-io/k3s/pull/5577
https://github.com/k3s-io/k3s/pull/5531
https://github.com/k3s-io/k3s/pull/5560

Types of Changes
backports
Verification
See linked issues
Linked Issues

TBD

User-Facing Change
The embedded ServiceLB LoadBalancer controller now supports mixed-protocol Services, and will clean up daemonsets when the Service type changes.
CNI plugins binaries now output the correct versions when queried on the command line
CNI plugins have been bumped to v1.1.1
K3s now uses the systemd cgroup driver instead of cgroupfs when running under systemd 244 or later.
K3s supervisor status errors are now wrapped in Kubernetes API error types, for improved compatibility with Kubernetes client libraries.
K3s now supports [NATS JetStream](https://docs.nats.io/nats-concepts/jetstream) as a datastore backend
The embedded kubelet now waits for the apiserver to become available before starting.
The K3s supervisor now implements a [KEP-1281](https://github.com/kubernetes/enhancements/tree/master/keps/sig-api-machinery/1281-network-proxy) compliant apiserver network proxy.
The integrated apiserver network proxy's operational mode can now be set with `--egress-selector-mode`.
When generating a replacement resolv.conf due to potentially unsuitable nameservers in the host resolv.conf, k3s now logs a warning, and stores the autogenerated configuration file in a more durable location.
Objects will be removed from Kubernetes when they are removed from manifest files.

Further Comments

Only failing check is DCO, and all the original commits are signed off so I'm not going to re-sign them all.


text:
[Feature]: Grafana dashboards as configmaps by default

Checklist

[X] I've searched for similar issues and couldn't find anything matching
[X] I've discussed this feature request in the K8sGPT Slack and got positive feedback

Is this feature request related to a problem?
No
Problem Description
No response
Solution Description
We should use the generated grafana/* dashboards from Kubebuilder to populate a new configmap e.g. config/grafana which has a kustomize overlay to inject the content into.
Benefits
Dashboards will show up for free if a use is using grafana
Potential Drawbacks
No response
Additional Information
No response

#65 #102 #105


text:
artms-515 change ipfamilypolicy

What this PR does:
IPv4/IPv6 dual-stack networking graduates to GA. Since 1.21, Kubernetes clusters are enabled to support dual-stack networking by default. In 1.23, the IPv6DualStack feature gate is removed.
For Headless Service , If the service doesn't have any selectors defined then it is defaulted to RequireDualStack on any cluster (single- or dual-stack)
https://github.com/kubernetes/kubernetes/blob/e6c093d87ea4cbb530a7b2ae91e54c0842d8308a/pkg/registry/core/service/storage/storage.go#L274
The two headless services we have to fix is
caas-cluster-seed-service
caas-cluster-dc-1-additional-seed-service

Which issue(s) this PR fixes:
Fixes #ARTMS-515
https://github.com/k8ssandra/cass-operator/issues/590
Checklist

[ ] Changes manually tested
[ ] Automated Tests added/updated
[ ] Documentation added/updated
[ ] CHANGELOG.md updated (not required for documentation PRs)
[ ] CLA Signed:  DataStax CLA

no need for this change


text:
Increment mCount only when read() succeeds

Implement skip which honors mLength.  Tidy up read(byte[], int, int).
Mark some members as final.

That's a lot of unrelated changes in one commit. I separated the different parts and committed them to master. Thanks!

Agreed that I should have broken up the changes into separate commits.  Thanks for doing this and simplifying the control flow!

authors: andrewgaul cketti


text:
Delete project-ds5010.py

Remove project-ds5010.py file because of naming conventions
As the name : project-ds5010.py is not working as expected to import into the test files we are deleting this file and creating two different files. A file for each class.

@Pappuru-Dinesh linter is throwing this error
media_filesize_estimator/mediaExtraction.py: note: In member "__init__" of class "Extraction":
media_filesize_estimator/mediaExtraction.py:35:25: error: Item "None" of "Optional[str]" has no attribute "split"
[union-attr]
                mimestart = mimestart.split("/")[0]
                            ^
Found 1 error in 1 file (checked 6 source files)
make: *** [mypy] Error 1

Any idea?

@Pappuru-Dinesh linter is throwing this error
media_filesize_estimator/mediaExtraction.py: note: In member "__init__" of class "Extraction":
media_filesize_estimator/mediaExtraction.py:35:25: error: Item "None" of "Optional[str]" has no attribute "split"
[union-attr]
                mimestart = mimestart.split("/")[0]
                            ^
Found 1 error in 1 file (checked 6 source files)
make: *** [mypy] Error 1

Any idea?

Fixed by adding # type ignore to that line of code

authors: Pappuru-Dinesh kHarshit

repo: kHarshit/media-filesize-estimator

license: MIT


text:
艦隊分析の艦隊情報反映のJSONフォーマットを出力させる

艦隊分析
艦娘を
[
  {
    "api_ship_id": id,
    "api_lv": lv,
    "api_kyouka": [k0, k1, k2, k3, k4, k5, k6],
    "api_sally_area": area
  },
  {...}
]

装備を
[
  {
    "api_slotitem_id": id,
    "api_level": lv
  },
  {...}
]

といった感じのjsonで登録できるようになってるっぽいのでそれのオプションを用意する

装備はそもそも艦娘関係ないのと本体に実装されたので無視でいいかな？
https://github.com/sanaehirotaka/logbook-kai/commit/2100e9b609545074e354acf7476a3ed76357c7b4

repo: kPherox/logbook-kanmusu-list-plugin


text:
【要望】一般信用在庫

長期用もデイトレ用も一般信用在庫を取得するAPIを作って欲しい！

在庫チェックは負荷が高いため、なかなか難しいところですが、ご要望として理解いたしました。

repo: kabucom/kabusapi


text:
Revise election app admin account topic, add images

@lsgunnlsgunn this can be merged

authors: Randynamic lsgunnlsgunn


text:
Update Klaytn Safe to Kaia Safe with new URL

Kindly update Klaytn Safe under Wallet / Multi-Sig section to Kaia Safe

Raised a PR https://github.com/kaiachain/awesome-kaia/pull/8

This issue has been fixed. Thanks to @snehasharma76 🎉

repo: kaiachain/awesome-kaia


text:
Can I set component show or hidden using schema?

Hello @kailong321200875
Is it possible to set component show or hidden using schema?
If so how can I do?

Actually, I am doing this like following.
const spanRef = ref(8)
const schema = [
  {
    ...
    colProps: {
      span: spanRef
    }
    ...
  },
  {
    ...
    onChange: (item) => {
      spanRef.value = (item === 'Y' ? 8 : 0)
    }
    ...
  }
]

But this is not good solution I think.
Let me know the better.

you can  set hidden: true


text:
kernel is not loading

Kairos version:

1.1.2
https://github.com/kairos-io/provider-kairos/releases/download/v1.1.2/kairos-alpine-arm-rpi-v1.1.2-k3sv1.25.2+k3s1.img
CPU architecture, OS, and Version:

aarch64, alpine flavor
Describe the bug

Can't boot on Rpi, get :
error: ../../grub-core/disk/loopback.c:98:device name already exists
error: ../../grub-core/loader/arm64/efi/linux.c:59:invalid magic number
error: ../..grub-core/loader/arm64/efi/linux.c:301:you need to load the kernel first

To Reproduce

Flash img to sd card (following docs) and boot Rpi
Expected behavior

Successful boot on Kairos
Logs

Additional context

I'm currently having a look as I have back an rpi4 at my hands. Checking out the repositories configuration currently and seems they are misconfigured and building against 32bit architecture. kudos to @jbalonso for the investigation. I'll follow up from there and check booting issues

This should be fixed now, the issue you reported is different from the one from @jbalonso, nevertheless, thanks for opening it up!

Still get issue with https://github.com/kairos-io/provider-kairos/releases/download/v1.1.3/kairos-alpine-arm-rpi-v1.1.3-k3sv1.25.2+k3s1.img

authors: Ludea mudler

repo: kairos-io/kairos


text:
:seedling: Support runtime registry authentication for updates

Is your feature request related to a problem? Please describe.
I'm currently evaluating Kairos and I pushed a customized OS image to a private registry. However currently there is no way for me to specify registry credentials when trying to run kairos-agent upgrade --image=....
Describe the solution you'd like
Some configuration location to specify registry credentials. For k3s-based images this can probably be integrated with secrets management, however my use case requires core images without k3s hence also an alternative secrets location.
Describe alternatives you've considered
Not sure there are any, let me know.
Additional context
N/A

Great point, thanks @shoop for filing the issue.
Currently this can be workarounded when upgrading manually with two steps:

elemental pull-image ...
elemental upgrade --system.uri dir:...

Nevertheless, the agent should expose a nicer way for this, and we should document how this works in Kubernetes

Great point, thanks @shoop for filing the issue.
Currently this can be workarounded when upgrading manually with two steps, similarly can be adapted for installations:
1. `elemental pull-image ...`

2. `elemental upgrade --system.uri dir:...`

Nevertheless, the agent should expose a nicer way for this, and we should document how this works in Kubernetes

That worked for me, thanks. Some more details for those not familiar with elemental:
mkdir tmp
sudo elemental pull-image --auth-server-address <registry-host> --auth-username <user> --auth-password <pass> \
  <registry-host>/kairos/kairos-ubuntu-22-lts:v1.6.1-k3sv1.24.10-k3s1-extended tmp/kairos.img
sudo elemental upgrade --system.uri dir:/home/kairos/tmp/kairos.img/

...then reboot.

@Itxaka I guess this needs still to be exposed in the upgrade command of the agent?

Yes. I hate how I cant link from one PR to an issue without github closing it :/

https://github.com/kairos-io/kairos/pull/1179 adds the correct flags into the upgrade command so they will be passed to elemental.

We still need a more decent way of passing this flags, maybe use env vars so they are not exposed in the command directly, but that would requires changes to the agent and elemental at the same time.
Auth stuff need to be reworked fully

authors: Itxaka jmaerki mudler shoop


text:
Contract test for pythonClass

This PR adds code to create Python classes from D and tests that Python receives them as it should.

Codecov Report

Merging #28 into master will increase coverage by 13.25%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##           master      #28       +/-   ##
===========================================
+ Coverage   20.89%   34.14%   +13.25%
===========================================
  Files           7        6        -1
  Lines          67       41       -26
===========================================
  Hits           14       14
+ Misses         53       27       -26

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update bfd6e71...eab66ff. Read the comment docs.

authors: atilaneves codecov-io

repo: kaleidicassociates/autowrap


text:
Returning false status for correct emails ids also...

Hi,
Thanks for the awesome gem... But in some cases it is returning false for correct email ids also.
Do we need to add any additional support to this gem to support latest data ??
If so, kindly let me know...
Thanks,
Mallikarjuna

in my case , its returning true for even wrong email ids!! i have same issues and ques. related to its working.

authors: APooja mallikarjunayaddala

license: mit

license_source: bigquery


text:
Break /client into /core /yoga /envelop /apollo

Closes #4571
Fixes #4570
Fixes #219
Fixes #3810

[x] update docs
[x] add README with migration guides
[ ] deprecate @graphql-hive/client (after stable release)
[ ] product update with migration story (after stable release)

https://the-guild.dev/graphql/hive/product-updates/2024-04-23-graphql-server-integrations-workers-support

repo: kamilkisiela/graphql-hive


text:
Not Work

Hello, I'm just try your script, its working but my views not increase. why?
Paste video url here: https://www.tiktok.com/@nthanfp/video/6881551033714216194
Made 10 successful shares
Made 20 successful shares
Made 30 successful shares
Made 40 successful shares
Made 50 successful shares
Made 60 successful shares
Made 70 successful shares
Made 80 successful shares
Made 90 successful shares
Made 100 successful shares
Made 110 successful shares
Made 120 successful shares

Hi, i just now updated a script, try it. For me it worked


text:
🛑 Covid19-nagano is down

In 16d081c, Covid19-nagano (https://covid19-nagano.info) was down:

HTTP code: 502
Response time: 504 ms

Resolved: Covid19-nagano is back up in bddac0c after 5 minutes.


text:
Next Up indicator shows up for Scaled Tokens

When I prepared pixies and scaled the token, the next up indicator showed up and spins for the latest token. There is no combat.

It happens after I scale a token. Copy/Paste a scaled token doesn't make this bug happen. Also, the starting indicator also shows up

repo: kandashi/Next-Up


text:
Add PodSecurity and ContainerSecurity params to PodOptions structure

Change Overview
Adding two new fields to the PodOptions structure will allow to configure security specification for a new pod in a more secure way and avoid using PodOverride parameter.
Also, the PR includes small fix for comments' formatting
Pull request type
Please check the type of change your PR introduces:

[x] :hamster: Trivial/Minor

Test Plan
Not sure if we need any tests here. Please let me know if you think we need to add some

@viveksinghggits @pavannd1 Guys, can we merge it?

I was only hesitant about introducing new field and not using podOverride. I will let @pavannd1 decide if it's acceptable, rest of the things are good.

authors: TimonOmsk viveksinghggits

repo: kanisterio/kanister


text:
Deprecate unused Helm releases

Signed-off-by: Rahul M Chheda rchheda@infracloud.io
Change Overview

Removed all the unused Helm Charts
Changed location of DockerFiles
Verified all changes via this commit: https://github.com/kanisterio/kanister/pull/719/commits/a636767313b6b33d0a6e853bbdbb8e2482b16b9e
Deprecated Push for un-used Helm charts

Please check the commit wise descriptions for more overview.

Pull request type
Please check the type of change your PR introduces:

[ ] :construction: Work in Progress
[ ] :rainbow: Refactoring (no functional changes, no api changes)
[ ] :hamster: Trivial/Minor
[ ] :bug: Bugfix
[ ] :sunflower: Feature
[ ] :world_map: Documentation
[x] :robot: Test

Issues

#XXX

Test Plan

[ ] :muscle: Manual
[ ] :zap: Unit test
[x] :green_heart: E2E

Whats up with the licenses file?

It came up when I ran the integration test, should I remove it?

I am not sure why integration test created that file, it shouldnt. Yes, I think we should remove that file.

I am not sure why integration test created that file, it shouldnt. Yes, I think we should remove that file.

Done @viveksinghggits

LGTM

authors: rahulchheda viveksinghggits


text:
enforce maximum individual blob size as 1 byte

When pack_blob returned a count > 255 binary encoding for the count byte overflows and loops around to 0 when 256 and so on. This patch fixes that.
For anyone else reading and considering using this project, I haven't had any other issues with this library (yet), have a ton of quickcheck tests and state machines on my end, and won't be using RPC, so am quite happy to recommend it even though it hasn't been maintained recently. We are working on a large-scale project that will most probably be using this, so it's entirely possible I could at some point take over maintenance (if that is even necessary).

Thanks for the fix, and the kind endorsement. :+1:

authors: kaos mokele

repo: kaos/ecapnp


text:
IntelliJ Gradle import fails when Kotlin 2.0.0-Beta4 is used

Moving from KMP 1.9.22 to 2.0.0-Beta4 fails the import process in IntelliJ IDEA.
* What went wrong:
Could not create task ':mocha:generateKarakumExternals'.
Could not create task of type 'KarakumGenerate'.
Could not generate a decorated class for type KarakumGenerate.
Cannot have abstract method RequiresNpmDependencies.getCompilation().

kotlin 2.0.0 It's also the same problem

try 1.0.0-alpha.40-K2

repo: karakum-team/karakum


text:
A process in the process pool was terminated abruptly while the future was running or pending

I finally got it running with python3.5 (tried for some time with python 2.7 but gave up).
I had to install python-magic and futures manually, but now I can run playlistlen --help without any import errors.
I'm getting this error now though:
$ playlistlen /volume1/video/Movies/

Filtering videos:   0%|                                                                                | 0/4 [00:00<?, ?it/s]
Traceback (most recent call last):
  File "/volume1/@appstore/py3k/usr/local/bin/playlistlen", line 11, in <module>
    sys.exit(main())
  File "/volume1/@appstore/py3k/usr/local/lib/python3.5/site-packages/playlist_length/main.py", line 159, in main
    result = video_len_calculator(args.path, args.no_subdir)
  File "/volume1/@appstore/py3k/usr/local/lib/python3.5/site-packages/playlist_length/main.py", line 100, in video_len_calculator
    path = task.result()
  File "/volume1/@appstore/py3k/usr/local/lib/python3.5/concurrent/futures/_base.py", line 398, in result
    return self.__get_result()
  File "/volume1/@appstore/py3k/usr/local/lib/python3.5/concurrent/futures/_base.py", line 357, in __get_result
    raise self._exception
concurrent.futures.process.BrokenProcessPool: A process in the process pool was terminated abruptly while the future was running or pending.

It seems to still be a 'magic' error I'm having. Manually running print(magic.from_file("video file path here", mime=True)) prints Aborted

It was python-magic (0.4.15) via pip.
I just tried with the package "filemagic" (1.6) instead, and it also imports correctly, but when I run a small test of magic.from_file() I now get:
Traceback (most recent call last):
  File "/volume1/@appstore/py3k/usr/local/bin/playlistlen", line 7, in <module>
    from playlist_length.main import main
  File "/volume1/@appstore/py3k/usr/local/lib/python3.5/site-packages/playlist_length/main.py", line 9, in <module>
    import magic
  File "/volume1/@appstore/py3k/usr/local/lib/python3.5/site-packages/magic/__init__.py", line 18, in <module>
    from magic.identify import Magic, MagicError
  File "/volume1/@appstore/py3k/usr/local/lib/python3.5/site-packages/magic/identify.py", line 16, in <module>
    from magic import api
  File "/volume1/@appstore/py3k/usr/local/lib/python3.5/site-packages/magic/api.py", line 22, in <module>
    raise ImportError('Unable to find magic library')
ImportError: Unable to find magic library

I thought it might be a problem with the libmagic library on this Synology server, so I just installed libmagic 5.25-2, but it hasn't changed anything.

Can you try installing python-magic with python3.5 -m pip install --user python-magic? and try again.. and yeah first uninstall python-magic

Did python3 -m pip install --user python-magic as my regular user, but still no luck.
print(magic.from_file("test.mp4", mime=True)) still simply prints "Aborted"
And running unmodified version of playlistlen now still gives me the same "concurrent.futures.process.BrokenProcessPool" exception.

Weird, print(magic.from_file("test.mp4", mime=True)) is this line raising some exception or simply printing Aborted?

It simply prints "Aborted".

I am closing this issue, for now you can raise an issue on python-magic repo because it seems your magic is not properly installed.

try installing libmagic  manually.

repo: karansthr/Playlist-Length


text:
Add final boss hang fix

Sometimes the game will hang if you draw the camera when you aim at Kirie. Can fix be added?

Done ;)


text:
留萠本線DLCへの対応

留萌本線DLCリリースによって実装された機能に追従するためのPRです。
90ecb3928fd31670ae3377680a7ccfc39c44bf07 では、新たに追加された「R (直結方向)」、「F (変速方向)」キーの割り当てを追加しています。
90ecb3928fd31670ae3377680a7ccfc39c44bf07 では、自動空気ブレーキ車(キハ54形)の特有の操作に対応するため、以下の割り当てでの「自動空気ブレーキ」モードを実装しています。
N → 運転 (M), B1 → 重なり (,), B2 → 常用 (.), B3 → 非常 (/), B4以上 → 無反応
使用するキーは2ハンドルと同じですが、ブレーキ操作はキーに対して直接機能が割り振られているため、2ハンドル用の処理を一部変更しています。
(sim上動作、キー出力ともに確認済み)
a145ecc8eac506877ab85420380f0275dc5f8d1f では、今回の変更内容に加えて一部記述を変更しています。
あわせてメイン画面画像の置き換えも行いたかったのですが、こちらは画像アップロード周りの挙動が変わっているようで確証が持てないため見送っています。

ありがとうございます。
帰宅後確認します。

authors: karasugawasu sorbatti


text:
remove results in a path not found exception when what you're trying to remove does not exist (v1.2.0.RC6)

With v1.2.0.RC6, remove results in a path not found exception if what you’re trying to remove doesn’t exist.  With versions RC5 and before it didn’t matter — the test would continue without error.  In other words, this scenario, which used to pass, now fails:
Scenario: com.jayway.jsonpath.PathNotFoundException with `remove`
  * def myRequest = {"a":"a"}
  * remove myRequest.b

will take this opportunity to bake the JS delete keyword into karate. over time, we will discourage use of remove.
as of today, this works:
* eval delete myRequest.b

we will make an enhancement so that this will work:
* delete myRequest.b

by the way, today we have baked if already. because it makes conditional logic a lot easier
* if (condition) karate.call('some.feature')

fixed in develop

Thanks again, Peter - works like a champ again!

1.2.0 released

authors: ptrthomas staffier

repo: karatelabs/karate


text:
Reconsider language support mode

Currently, it is possible to set a language within the Context, which has its negatives. As an alternative, consider instead adding support to filter certain fields by language using the find method and the where specification.

Resolved by #80.

repo: karelklima/ldkit


text:
Lambda details

Tidy up and standardise spacing between things
Add aws-regions.txt as it appears to be the same regardless of parameters passed (as suggested in doc)
Update README
Add flag to output number of versions and name of lambda being worked on

Hi @carlgarner, thanks for the PR. I'm gonna review these changes later today when I get a moment. Two things that stand out. The readme update, we need to have that file generated locally to compile. That's how we add support for new AWS regions, by querying the EC2 API and getting the list during compile.
The other question I have is about IBytes. What is the benefit of switching over to IBytes?

Fair point on the regions, though I don't believe they change that frequently. You could keep this stored to simplify the build process, but equally, is it really needed? A user would know what region they're operating in and this would either be part of their profile (if they've chosen to set a default) or something they know and are happy passing at run-time.
As to the IBytes, Bytes uses the 1000 multiplier and IBytes is 1024. I would argue that most are used to seeing things in the 1024 format, however, I'd changed this because I believe there may be a calculation error somewhere. When running the app against the account I'm working with, the Lambda usage is ~69Gb, yet the dryrun report was claiming a value ~77Gb. I hadn't got to the bottom of this when I made the PR which was meant to be, largely, for the version count and lambda details.
Unfortunately, I haven't got much further with it. This is a first foray into GoLang as well.

@carlgarner I've been thinking about this change, and it's technically breaking change.  I'm gonna move this PR into a new branch. I want to abstract some things out to avoid changing the changes for existing users. I'll tag you when it's ready for review. Your changes will carry over to this branch.

authors: carlgarner karl-cardenas-coding

repo: karl-cardenas-coding/go-lambda-cleanup


text:
Add privacy section

Resolves #5

Until there is more data about overlays using cookies to track users, that part can't be verified. At least one of the worst offenders does not seem to use cookies to track users - no persistent data is stored in their cookies at any rate.
What we do know is that these overlays track users on the websites they're enabled on (by "tracking clicks and heatmaps" according to one vendor), and that the scripts that do this are loaded from the vendor's servers. So that, in addition to browser fingerprinting, overlay companies have a centralised way to track users across websites that use their overlays without needing to use cookies at all.

Until there is more data about overlays using cookies to track users, that part can't be verified. At least one of the worst offenders does not seem to use cookies to track users - no persistent data is stored in their cookies at any rate.
What we do know is that these overlays track users on the websites they're enabled on (by "tracking clicks and heatmaps" according to one vendor), and that the scripts that do this are loaded from the vendor's servers. So that, in addition to browser fingerprinting, overlay companies have a centralised way to track users across websites that use their overlays without needing to use cookies at all.

Let's put on a darker hat..
It's not only about the overlay provider potentially using this data.
Any tracker could add code that fingerprints someone that interacts with a known overlay (or general code sample to i.e. increase font-size).

Let's put on a darker hat..
It's not only about the overlay provider potentially using this data.
Any tracker could add code that fingerprints someone that interacts with a known overlay (or general code sample to i.e. increase font-size).

Yes, they could, but that is not unique to overlays. The same is true for legitimate scripts that provide accessibility - like the greasemonkey scripts provided by NVAccess for example.
Unless there is evidence that overlays are being hijacked in this way, then it is speculative at best - and that risks undermining the credibility of this "non-biased, community-driven, fact-based information sheet".

Closing in deference to an updated PR

authors: Aircl0wn LJWatson karlgroves

repo: karlgroves/overlayfactsheet


text:
Fix passing options to BrowserstackLocal

https://github.com/karma-runner/karma-browserstack-launcher/commit/ea4ec78352d8829742ae3e96b42944f96d0174e8 broke passing most arguments to BrowserstackLocal. Only key is being passed in now.

Same issue here

authors: dweedon-stripe jeremad


text:
update readme

กระต่ายกลมๆ น่ากิน

กระต่ายอร่อย

ใช่

Okayyyy

authors: ChillZPHZ karnhao

repo: karnhao/HaoDiscordBot


text:
Fe homework 16

Metric
Value

alert_status
:white_check_mark: OK

bugs
1

code_smells
1

reliability_rating
B (at least 1 Minor Bug)Note: A being best, E being worst

security_rating
A (0 Vulnerabilities)Note: A being best, E being worst

vulnerabilities
0


text:
kubestr should support volumeMode: Block

I could not find any information in the docs that would allow me to use volumeMode: Block and issue the benchmark against a devicePath instead of a mountPath.

@datamattsson Currently we only run FIO against Filesystem volumeMode. I think that supporting volumeMode Block is a good request. We will post an update here when we support that functionality. Thanks!

Interesting if it does not replace the filesystem mode. Else we wouldn't be able to benchmark RWX like NFS/CephFS/Gluster/...

authors: AlexisDucastel bathina2 datamattsson

repo: kastenhq/kubestr


text:
Kata Containers 1.11.5

Version bump no changes

/test-ubuntu

authors: amshinde katabuilder

repo: kata-containers/agent


text:
Failed to luanch android image based on kata

Description of problem

Enable host OS binder driver and ashmem then launch android image by runc successfully;

Rebuild kata guest kernel and add two android depending on modelers: binder driver and ashmem and then failed to launch the same android image by kata;

Expected result
launch the same android image by kata successfully;
Actual result
Meta details
Running kata-collect-data.sh version 1.6.0-rc1 (commit 9f8d4e1) at 2019-04-17.17:43:19.365712194+0800.

Runtime is /usr/bin/kata-runtime.
kata-env
Output of "/usr/bin/kata-runtime kata-env":
[Meta]
  Version = "1.0.20"

[Runtime]
  Debug = true
  Trace = false
  DisableGuestSeccomp = true
  DisableNewNetNs = false
  Path = "/usr/bin/kata-runtime"
  [Runtime.Version]
    Semver = "1.6.0-rc1"
    Commit = "9f8d4e1"
    OCI = "1.0.1-dev"
  [Runtime.Config]
    Path = "/usr/share/defaults/kata-containers/configuration.toml"

[Hypervisor]
  MachineType = "pc"
  Version = "QEMU emulator version 2.11.0\nCopyright (c) 2003-2017 Fabrice Bellard and the QEMU Project developers"
  Path = "/usr/bin/qemu-lite-system-x86_64"
  BlockDeviceDriver = "virtio-scsi"
  EntropySource = "/dev/urandom"
  Msize9p = 8192
  MemorySlots = 10
  Debug = false
  UseVSock = false

[Image]
  Path = "/usr/share/kata-containers/kata-containers-image_clearlinux_1.6.0-rc1_agent_a2037c08531.img"

[Kernel]
  Path = "/usr/share/kata-containers/kata-vmlinuz-4.14-andriod.container"
  Parameters = "init=/usr/lib/systemd/systemd systemd.unit=kata-containers.target systemd.mask=systemd-networkd.service systemd.mask=systemd-networkd.socket"

[Initrd]
  Path = ""

[Proxy]
  Type = "kataProxy"
  Version = "kata-proxy version 1.6.0-rc1-2085829"
  Path = "/usr/libexec/kata-containers/kata-proxy"
  Debug = true

[Shim]
  Type = "kataShim"
  Version = "kata-shim version 1.6.0-rc1-0f41347"
  Path = "/usr/libexec/kata-containers/kata-shim"
  Debug = true

[Agent]
  Type = "kata"

[Host]
  Kernel = "3.10.0-862.el7.x86_64"
  Architecture = "amd64"
  VMContainerCapable = true
  SupportVSocks = false
  [Host.Distro]
    Name = "CentOS Linux"
    Version = "7"
  [Host.CPU]
    Vendor = "GenuineIntel"
    Model = "Intel(R) Xeon(R) CPU E5-2680 v4 @ 2.40GHz"

[Netmon]
  Version = "kata-netmon version 1.6.0-rc1"
  Path = "/usr/libexec/kata-containers/kata-netmon"
  Debug = false
  Enable = false

Runtime config files
Runtime default config files
/etc/kata-containers/configuration.toml
/usr/share/defaults/kata-containers/configuration.toml

Runtime config file contents
Config file /etc/kata-containers/configuration.toml not found
Output of "cat "/usr/share/defaults/kata-containers/configuration.toml"":
# Copyright (c) 2017-2019 Intel Corporation
#
# SPDX-License-Identifier: Apache-2.0
#

# XXX: WARNING: this file is auto-generated.
# XXX:
# XXX: Source file: "cli/config/configuration-qemu.toml.in"
# XXX: Project:
# XXX:   Name: Kata Containers
# XXX:   Type: kata

[hypervisor.qemu]
path = "/usr/bin/qemu-lite-system-x86_64"
#kernel = "/usr/share/kata-containers/vmlinuz.container"
kernel = "/usr/share/kata-containers/vmlinuz-andriod.container"
image = "/usr/share/kata-containers/kata-containers.img"
machine_type = "pc"

# Optional space-separated list of options to pass to the guest kernel.
# For example, use `kernel_params = "vsyscall=emulate"` if you are having
# trouble running pre-2.15 glibc.
#
# WARNING: - any parameter specified here will take priority over the default
# parameter value of the same name used to start the virtual machine.
# Do not set values here unless you understand the impact of doing so as you
# may stop the virtual machine from booting.
# To see the list of default parameters, enable hypervisor debug, create a
# container and look for 'default-kernel-parameters' log entries.
kernel_params = ""

# Path to the firmware.
# If you want that qemu uses the default firmware leave this option empty
firmware = ""

# Machine accelerators
# comma-separated list of machine accelerators to pass to the hypervisor.
# For example, `machine_accelerators = "nosmm,nosmbus,nosata,nopit,static-prt,nofw"`
machine_accelerators=""

# Default number of vCPUs per SB/VM:
# unspecified or 0                --> will be set to 1
# < 0                             --> will be set to the actual number of physical cores
# > 0 <= number of physical cores --> will be set to the specified number
# > number of physical cores      --> will be set to the actual number of physical cores
default_vcpus = 1

# Default maximum number of vCPUs per SB/VM:
# unspecified or == 0             --> will be set to the actual number of physical cores or to the maximum number
#                                     of vCPUs supported by KVM if that number is exceeded
# > 0 <= number of physical cores --> will be set to the specified number
# > number of physical cores      --> will be set to the actual number of physical cores or to the maximum number
#                                     of vCPUs supported by KVM if that number is exceeded
# WARNING: Depending of the architecture, the maximum number of vCPUs supported by KVM is used when
# the actual number of physical cores is greater than it.
# WARNING: Be aware that this value impacts the virtual machine's memory footprint and CPU
# the hotplug functionality. For example, `default_maxvcpus = 240` specifies that until 240 vCPUs
# can be added to a SB/VM, but the memory footprint will be big. Another example, with
# `default_maxvcpus = 8` the memory footprint will be small, but 8 will be the maximum number of
# vCPUs supported by the SB/VM. In general, we recommend that you do not edit this variable,
# unless you know what are you doing.
default_maxvcpus = 0

# Bridges can be used to hot plug devices.
# Limitations:
# * Currently only pci bridges are supported
# * Until 30 devices per bridge can be hot plugged.
# * Until 5 PCI bridges can be cold plugged per VM.
#   This limitation could be a bug in qemu or in the kernel
# Default number of bridges per SB/VM:
# unspecified or 0   --> will be set to 1
# > 1 <= 5           --> will be set to the specified number
# > 5                --> will be set to 5
default_bridges = 1

# Default memory size in MiB for SB/VM.
# If unspecified then it will be set 2048 MiB.
default_memory = 2048
#
# Default memory slots per SB/VM.
# If unspecified then it will be set 10.
# This is will determine the times that memory will be hotadded to sandbox/VM.
#memory_slots = 10

# The size in MiB will be plused to max memory of hypervisor.
# It is the memory address space for the NVDIMM devie.
# If set block storage driver (block_device_driver) to "nvdimm",
# should set memory_offset to the size of block device.
# Default 0
#memory_offset = 0

# Disable block device from being used for a container's rootfs.
# In case of a storage driver like devicemapper where a container's
# root file system is backed by a block device, the block device is passed
# directly to the hypervisor for performance reasons.
# This flag prevents the block device from being passed to the hypervisor,
# 9pfs is used instead to pass the rootfs.
disable_block_device_use = false

# Block storage driver to be used for the hypervisor in case the container
# rootfs is backed by a block device. This is virtio-scsi, virtio-blk
# or nvdimm.
block_device_driver = "virtio-scsi"

# Specifies cache-related options will be set to block devices or not.
# Default false
#block_device_cache_set = true

# Specifies cache-related options for block devices.
# Denotes whether use of O_DIRECT (bypass the host page cache) is enabled.
# Default false
#block_device_cache_direct = true

# Specifies cache-related options for block devices.
# Denotes whether flush requests for the device are ignored.
# Default false
#block_device_cache_noflush = true

# Enable iothreads (data-plane) to be used. This causes IO to be
# handled in a separate IO thread. This is currently only implemented
# for SCSI.
#
enable_iothreads = false

# Enable pre allocation of VM RAM, default false
# Enabling this will result in lower container density
# as all of the memory will be allocated and locked
# This is useful when you want to reserve all the memory
# upfront or in the cases where you want memory latencies
# to be very predictable
# Default false
#enable_mem_prealloc = true

# Enable huge pages for VM RAM, default false
# Enabling this will result in the VM memory
# being allocated using huge pages.
# This is useful when you want to use vhost-user network
# stacks within the container. This will automatically
# result in memory pre allocation
#enable_hugepages = true

# Enable swap of vm memory. Default false.
# The behaviour is undefined if mem_prealloc is also set to true
#enable_swap = true

# This option changes the default hypervisor and kernel parameters
# to enable debug output where available. This extra output is added
# to the proxy logs, but only when proxy debug is also enabled.
#
# Default false
#enable_debug = true

# Disable the customizations done in the runtime when it detects
# that it is running on top a VMM. This will result in the runtime
# behaving as it would when running on bare metal.
#
#disable_nesting_checks = true

# This is the msize used for 9p shares. It is the number of bytes
# used for 9p packet payload.
#msize_9p = 8192

# If true and vsocks are supported, use vsocks to communicate directly
# with the agent and no proxy is started, otherwise use unix
# sockets and start a proxy to communicate with the agent.
# Default false
#use_vsock = true

# VFIO devices are hotplugged on a bridge by default.
# Enable hotplugging on root bus. This may be required for devices with
# a large PCI bar, as this is a current limitation with hotplugging on
# a bridge. This value is valid for "pc" machine type.
# Default false
#hotplug_vfio_on_root_bus = true

# If host doesn't support vhost_net, set to true. Thus we won't create vhost fds for nics.
# Default false
#disable_vhost_net = true
#
# Default entropy source.
# The path to a host source of entropy (including a real hardware RNG)
# /dev/urandom and /dev/random are two main options.
# Be aware that /dev/random is a blocking source of entropy.  If the host
# runs out of entropy, the VMs boot time will increase leading to get startup
# timeouts.
# The source of entropy /dev/urandom is non-blocking and provides a
# generally acceptable source of entropy. It should work well for pretty much
# all practical purposes.
#entropy_source= "/dev/urandom"

# Path to OCI hook binaries in the *guest rootfs*.
# This does not affect host-side hooks which must instead be added to
# the OCI spec passed to the runtime.
#
# You can create a rootfs with hooks by customizing the osbuilder scripts:
# https://github.com/kata-containers/osbuilder
#
# Hooks must be stored in a subdirectory of guest_hook_path according to their
# hook type, i.e. "guest_hook_path/{prestart,postart,poststop}".
# The agent will scan these directories for executable files and add them, in
# lexicographical order, to the lifecycle of the guest container.
# Hooks are executed in the runtime namespace of the guest. See the official documentation:
# https://github.com/opencontainers/runtime-spec/blob/v1.0.1/config.md#posix-platform-hooks
# Warnings will be logged if any error is encountered will scanning for hooks,
# but it will not abort container execution.
#guest_hook_path = "/usr/share/oci/hooks"

[factory]
# VM templating support. Once enabled, new VMs are created from template
# using vm cloning. They will share the same initial kernel, initramfs and
# agent memory by mapping it readonly. It helps speeding up new container
# creation and saves a lot of memory if there are many kata containers running
# on the same host.
#
# When disabled, new VMs are created from scratch.
#
# Note: Requires "initrd=" to be set ("image=" is not supported).
#
# Default false
#enable_template = true

[proxy.kata]
path = "/usr/libexec/kata-containers/kata-proxy"

# If enabled, proxy messages will be sent to the system log
# (default: disabled)
enable_debug = true

[shim.kata]
path = "/usr/libexec/kata-containers/kata-shim"

# If enabled, shim messages will be sent to the system log
# (default: disabled)
enable_debug = true

# If enabled, the shim will create opentracing.io traces and spans.
# (See https://www.jaegertracing.io/docs/getting-started).
#
# Note: By default, the shim runs in a separate network namespace. Therefore,
# to allow it to send trace details to the Jaeger agent running on the host,
# it is necessary to set 'disable_new_netns=true' so that it runs in the host
# network namespace.
#
# (default: disabled)
#enable_tracing = true

[agent.kata]
# There is no field for this section. The goal is only to be able to
# specify which type of agent the user wants to use.

[netmon]
# If enabled, the network monitoring process gets started when the
# sandbox is created. This allows for the detection of some additional
# network being added to the existing network namespace, after the
# sandbox has been created.
# (default: disabled)
#enable_netmon = true

# Specify the path to the netmon binary.
path = "/usr/libexec/kata-containers/kata-netmon"

# If enabled, netmon messages will be sent to the system log
# (default: disabled)
#enable_debug = true

[runtime]
# If enabled, the runtime will log additional debug messages to the
# system log
# (default: disabled)
enable_debug = true
#
# Internetworking model
# Determines how the VM should be connected to the
# the container network interface
# Options:
#
#   - bridged
#     Uses a linux bridge to interconnect the container interface to
#     the VM. Works for most cases except macvlan and ipvlan.
#
#   - macvtap
#     Used when the Container network interface can be bridged using
#     macvtap.
#
#   - none
#     Used when customize network. Only creates a tap device. No veth pair.
#
#   - tcfilter
#     Uses tc filter rules to redirect traffic from the network interface
#     provided by plugin to a tap interface connected to the VM.
#
internetworking_model="macvtap"

# disable guest seccomp
# Determines whether container seccomp profiles are passed to the virtual
# machine and applied by the kata agent. If set to true, seccomp is not applied
# within the guest
# (default: true)
disable_guest_seccomp=true

# If enabled, the runtime will create opentracing.io traces and spans.
# (See https://www.jaegertracing.io/docs/getting-started).
# (default: disabled)
#enable_tracing = true

# If enabled, the runtime will not create a network namespace for shim and hypervisor processes.
# This option may have some potential impacts to your host. It should only be used when you know what you're doing.
# `disable_new_netns` conflicts with `enable_netmon`
# `disable_new_netns` conflicts with `internetworking_model=bridged` and `internetworking_model=macvtap`. It works only
# with `internetworking_model=none`. The tap device will be in the host network namespace and can connect to a bridge
# (like OVS) directly.
# If you are using docker, `disable_new_netns` only works with `docker run --net=none`
# (default: false)
#disable_new_netns = true

KSM throttler
version
Output of "/usr/libexec/kata-ksm-throttler/kata-ksm-throttler --version":
kata-ksm-throttler version 1.6.0-rc1-ce5b765

Output of "/usr/lib/systemd/system/kata-ksm-throttler.service --version":
/usr/bin/kata-collect-data.sh: line 168: /usr/lib/systemd/system/kata-ksm-throttler.service: Permission denied

systemd service
Image details
---
osbuilder:
  url: "https://github.com/kata-containers/osbuilder"
  version: "unknown"
rootfs-creation-time: "2019-03-04T21:52:40.031090715+0000Z"
description: "osbuilder rootfs"
file-format-version: "0.0.2"
architecture: "x86_64"
base-distro:
  name: "Clear"
  version: "28100"
  packages:
    default:
      - "iptables-bin"
      - "libudev0-shim"
      - "systemd"
    extra:

agent:
  url: "https://github.com/kata-containers/agent"
  name: "kata-agent"
  version: "1.6.0-rc1-a2037c08531e4982003d8fc9b4837d27c35c0966"
  agent-is-init-daemon: "no"

Initrd details
No initrd

320284d29c85c2 name=kata-runtime pid=272038 source=virtcontainers subsystem=kata_agent
time="2019-04-15T16:43:56.959834186+08:00" level=warning msg="load sandbox devices failed" arch=amd64 command=create container=3122d618a896589702f918616847f014ae48030eba0e7f2df2320284d29c8
5c2 error="open /run/vc/sbs/3122d618a896589702f918616847f014ae48030eba0e7f2df2320284d29c85c2/devices.json: no such file or directory" name=kata-runtime pid=272038 sandbox=3122d618a89658970
2f918616847f014ae48030eba0e7f2df2320284d29c85c2 sandboxid=3122d618a896589702f918616847f014ae48030eba0e7f2df2320284d29c85c2 source=virtcontainers subsystem=sandbox
time="2019-04-16T17:07:44.438555073+08:00" level=debug msg="Could not retrieve anything from storage" arch=amd64 command=create container=6d4b102a48e19d90eeb1ecc753c2ed246ca8d3f7f4d0840ea8
88207b1addb6b7 name=kata-runtime pid=82304 source=virtcontainers subsystem=kata_agent
time="2019-04-16T17:07:44.438599578+08:00" level=warning msg="load sandbox devices failed" arch=amd64 command=create container=6d4b102a48e19d90eeb1ecc753c2ed246ca8d3f7f4d0840ea888207b1addb
6b7 error="open /run/vc/sbs/6d4b102a48e19d90eeb1ecc753c2ed246ca8d3f7f4d0840ea888207b1addb6b7/devices.json: no such file or directory" name=kata-runtime pid=82304 sandbox=6d4b102a48e19d90ee
b1ecc753c2ed246ca8d3f7f4d0840ea888207b1addb6b7 sandboxid=6d4b102a48e19d90eeb1ecc753c2ed246ca8d3f7f4d0840ea888207b1addb6b7 source=virtcontainers subsystem=sandbox
time="2019-04-16T17:07:45.91855327+08:00" level=info msg="{"error": {"class": "GenericError", "desc": "Could not open '/dev/fd0': No such device or address"}}" arch=amd64 command
=create container=6d4b102a48e19d90eeb1ecc753c2ed246ca8d3f7f4d0840ea888207b1addb6b7 name=kata-runtime pid=82304 source=virtcontainers subsystem=qmp
time="2019-04-16T17:07:46.00200023+08:00" level=error msg="QMP command failed: Could not open '/dev/fd0': No such device or address" arch=amd64 command=create container=6d4b102a48e19d90eeb
1ecc753c2ed246ca8d3f7f4d0840ea888207b1addb6b7 name=kata-runtime pid=82304 source=runtime
time="2019-04-16T17:07:58.932782354+08:00" level=debug msg="Could not retrieve anything from storage" arch=amd64 command=create container=2b20edf0dc79b902b096386202f8b37caf27f1badfa8085d33
84dd251ad75d28 name=kata-runtime pid=82403 source=virtcontainers subsystem=kata_agent
time="2019-04-16T17:07:58.932821958+08:00" level=warning msg="load sandbox devices failed" arch=amd64 command=create container=2b20edf0dc79b902b096386202f8b37caf27f1badfa8085d3384dd251ad75
d28 error="open /run/vc/sbs/2b20edf0dc79b902b096386202f8b37caf27f1badfa8085d3384dd251ad75d28/devices.json: no such file or directory" name=kata-runtime pid=82403 sandbox=2b20edf0dc79b902b0
96386202f8b37caf27f1badfa8085d3384dd251ad75d28 sandboxid=2b20edf0dc79b902b096386202f8b37caf27f1badfa8085d3384dd251ad75d28 source=virtcontainers subsystem=sandbox
time="2019-04-16T17:08:00.261576928+08:00" level=info msg="{"error": {"class": "GenericError", "desc": "Could not open '/dev/fd0': No such device or address"}}" arch=amd64 comman
d=create container=2b20edf0dc79b902b096386202f8b37caf27f1badfa8085d3384dd251ad75d28 name=kata-runtime pid=82403 source=virtcontainers subsystem=qmp
time="2019-04-16T17:08:00.28784754+08:00" level=error msg="QMP command failed: Could not open '/dev/fd0': No such device or address" arch=amd64 command=create container=2b20edf0dc79b902b09
6386202f8b37caf27f1badfa8085d3384dd251ad75d28 name=kata-runtime pid=82403 source=runtime
time="2019-04-16T17:17:32.642085739+08:00" level=debug msg="Could not retrieve anything from storage" arch=amd64 command=create container=37cb8ad988f540887bd9aa44d178c207f4d93f5dd44220c09f
0a4356465a9e0d name=kata-runtime pid=83072 source=virtcontainers subsystem=kata_agent
time="2019-04-16T17:17:32.642133575+08:00" level=warning msg="load sandbox devices failed" arch=amd64 command=create container=37cb8ad988f540887bd9aa44d178c207f4d93f5dd44220c09f0a4356465a9
e0d error="open /run/vc/sbs/37cb8ad988f540887bd9aa44d178c207f4d93f5dd44220c09f0a4356465a9e0d/devices.json: no such file or directory" name=kata-runtime pid=83072 sandbox=37cb8ad988f540887b
d9aa44d178c207f4d93f5dd44220c09f0a4356465a9e0d sandboxid=37cb8ad988f540887bd9aa44d178c207f4d93f5dd44220c09f0a4356465a9e0d source=virtcontainers subsystem=sandbox
time="2019-04-16T17:17:34.013555599+08:00" level=info msg="{"error": {"class": "GenericError", "desc": "Could not open '/dev/fd0': No such device or address"}}" arch=amd64 comman
d=create container=37cb8ad988f540887bd9aa44d178c207f4d93f5dd44220c09f0a4356465a9e0d name=kata-runtime pid=83072 source=virtcontainers subsystem=qmp
time="2019-04-16T17:17:34.040044399+08:00" level=error msg="QMP command failed: Could not open '/dev/fd0': No such device or address" arch=amd64 command=create container=37cb8ad988f540887b
d9aa44d178c207f4d93f5dd44220c09f0a4356465a9e0d name=kata-runtime pid=83072 source=runtime
time="2019-04-16T17:18:20.403285719+08:00" level=debug msg="Could not retrieve anything from storage" arch=amd64 command=create container=c727a814256d307b45a49fe7cb4822bffe418037577b968d2f
37bef37fb21267 name=kata-runtime pid=83190 source=virtcontainers subsystem=kata_agent
time="2019-04-16T17:18:20.403328737+08:00" level=warning msg="load sandbox devices failed" arch=amd64 command=create container=c727a814256d307b45a49fe7cb4822bffe418037577b968d2f37bef37fb21
267 error="open /run/vc/sbs/c727a814256d307b45a49fe7cb4822bffe418037577b968d2f37bef37fb21267/devices.json: no such file or directory" name=kata-runtime pid=83190 sandbox=c727a814256d307b45
a49fe7cb4822bffe418037577b968d2f37bef37fb21267 sandboxid=c727a814256d307b45a49fe7cb4822bffe418037577b968d2f37bef37fb21267 source=virtcontainers subsystem=sandbox
time="2019-04-16T17:18:21.705482712+08:00" level=info msg="{"error": {"class": "GenericError", "desc": "Could not open '/dev/fd0': No such device or address"}}" arch=amd64 comman
d=create container=c727a814256d307b45a49fe7cb4822bffe418037577b968d2f37bef37fb21267 name=kata-runtime pid=83190 source=virtcontainers subsystem=qmp
time="2019-04-16T17:18:21.760923996+08:00" level=error msg="QMP command failed: Could not open '/dev/fd0': No such device or address" arch=amd64 command=create container=c727a814256d307b45
a49fe7cb4822bffe418037577b968d2f37bef37fb21267 name=kata-runtime pid=83190 source=runtime
time="2019-04-16T17:23:14.254669589+08:00" level=debug msg="Could not retrieve anything from storage" arch=amd64 command=create container=d4c091664726ad991659f8e28e8e238b931e9f95a303cb6c39
01eac4e389fcd6 name=kata-runtime pid=83809 source=virtcontainers subsystem=kata_agent
time="2019-04-16T17:23:14.254709281+08:00" level=warning msg="load sandbox devices failed" arch=amd64 command=create container=d4c091664726ad991659f8e28e8e238b931e9f95a303cb6c3901eac4e389f
cd6 error="open /run/vc/sbs/d4c091664726ad991659f8e28e8e238b931e9f95a303cb6c3901eac4e389fcd6/devices.json: no such file or directory" name=kata-runtime pid=83809 sandbox=d4c091664726ad9916
59f8e28e8e238b931e9f95a303cb6c3901eac4e389fcd6 sandboxid=d4c091664726ad991659f8e28e8e238b931e9f95a303cb6c3901eac4e389fcd6 source=virtcontainers subsystem=sandbox
time="2019-04-16T17:23:15.621579547+08:00" level=info msg="{"error": {"class": "GenericError", "desc": "Could not open '/dev/fd0': No such device or address"}}" arch=amd64 comman
d=create container=d4c091664726ad991659f8e28e8e238b931e9f95a303cb6c3901eac4e389fcd6 name=kata-runtime pid=83809 source=virtcontainers subsystem=qmp
time="2019-04-16T17:23:15.647877804+08:00" level=error msg="QMP command failed: Could not open '/dev/fd0': No such device or address" arch=amd64 command=create container=d4c091664726ad9916
59f8e28e8e238b931e9f95a303cb6c3901eac4e389fcd6 name=kata-runtime pid=83809 source=runtime
time="2019-04-17T15:52:11.762224737+08:00" level=debug msg="Could not retrieve anything from storage" arch=amd64 command=create container=d2e84d608f77a85c98f1d37115254a6e0b769b020ee111455a
1412d92b45904b name=kata-runtime pid=166837 source=virtcontainers subsystem=kata_agent
time="2019-04-17T15:52:11.762283796+08:00" level=warning msg="load sandbox devices failed" arch=amd64 command=create container=d2e84d608f77a85c98f1d37115254a6e0b769b020ee111455a1412d92b459
04b error="open /run/vc/sbs/d2e84d608f77a85c98f1d37115254a6e0b769b020ee111455a1412d92b45904b/devices.json: no such file or directory" name=kata-runtime pid=166837 sandbox=d2e84d608f77a85c9
8f1d37115254a6e0b769b020ee111455a1412d92b45904b sandboxid=d2e84d608f77a85c98f1d37115254a6e0b769b020ee111455a1412d92b45904b source=virtcontainers subsystem=sandbox
time="2019-04-17T15:52:13.130480717+08:00" level=info msg="{"error": {"class": "GenericError", "desc": "Could not open '/dev/fd0': No such device or address"}}" arch=amd64 comman
d=create container=d2e84d608f77a85c98f1d37115254a6e0b769b020ee111455a1412d92b45904b name=kata-runtime pid=166837 source=virtcontainers subsystem=qmp
time="2019-04-17T15:52:13.15586313+08:00" level=error msg="QMP command failed: Could not open '/dev/fd0': No such device or address" arch=amd64 command=create container=d2e84d608f77a85c98f
1d37115254a6e0b769b020ee111455a1412d92b45904b name=kata-runtime pid=166837 source=runtime
time="2019-04-17T16:34:43.829706497+08:00" level=debug msg="Could not retrieve anything from storage" arch=amd64 command=create container=a98c2d8a7bb80dca033eca387ba837754f55316876411dae7e
4c0fad1600021b name=kata-runtime pid=169567 source=virtcontainers subsystem=kata_agent
time="2019-04-17T16:34:43.829758305+08:00" level=warning msg="load sandbox devices failed" arch=amd64 command=create container=a98c2d8a7bb80dca033eca387ba837754f55316876411dae7e4c0fad16000
21b error="open /run/vc/sbs/a98c2d8a7bb80dca033eca387ba837754f55316876411dae7e4c0fad1600021b/devices.json: no such file or directory" name=kata-runtime pid=169567 sandbox=a98c2d8a7bb80dca0
33eca387ba837754f55316876411dae7e4c0fad1600021b sandboxid=a98c2d8a7bb80dca033eca387ba837754f55316876411dae7e4c0fad1600021b source=virtcontainers subsystem=sandbox
time="2019-04-17T16:34:45.179639719+08:00" level=info msg="{"error": {"class": "GenericError", "desc": "Could not open '/dev/fd0': No such device or address"}}" arch=amd64 comman
d=create container=a98c2d8a7bb80dca033eca387ba837754f55316876411dae7e4c0fad1600021b name=kata-runtime pid=169567 source=virtcontainers subsystem=qmp
time="2019-04-17T16:34:45.200887173+08:00" level=error msg="QMP command failed: Could not open '/dev/fd0': No such device or address" arch=amd64 command=create container=a98c2d8a7bb80dca03
3eca387ba837754f55316876411dae7e4c0fad1600021b name=kata-runtime pid=169567 source=runtime
time="2019-04-17T16:35:07.581504419+08:00" level=debug msg="Could not retrieve anything from storage" arch=amd64 command=create container=5b3633d8595090c15d16429796858e4856e0b4b542408a48a2
5a7fdb454f3062 name=kata-runtime pid=169665 source=virtcontainers subsystem=kata_agent
time="2019-04-17T16:35:07.581544822+08:00" level=warning msg="load sandbox devices failed" arch=amd64 command=create container=5b3633d8595090c15d16429796858e4856e0b4b542408a48a25a7fdb454f3
062 error="open /run/vc/sbs/5b3633d8595090c15d16429796858e4856e0b4b542408a48a25a7fdb454f3062/devices.json: no such file or directory" name=kata-runtime pid=169665 sandbox=5b3633d8595090c15
d16429796858e4856e0b4b542408a48a25a7fdb454f3062 sandboxid=5b3633d8595090c15d16429796858e4856e0b4b542408a48a25a7fdb454f3062 source=virtcontainers subsystem=sandbox
time="2019-04-17T16:35:08.922462833+08:00" level=info msg="{"error": {"class": "GenericError", "desc": "Could not open '/dev/fd0': No such device or address"}}" arch=amd64 comman
d=create container=5b3633d8595090c15d16429796858e4856e0b4b542408a48a25a7fdb454f3062 name=kata-runtime pid=169665 source=virtcontainers subsystem=qmp
time="2019-04-17T16:35:08.94287472+08:00" level=error msg="QMP command failed: Could not open '/dev/fd0': No such device or address" arch=amd64 command=create container=5b3633d8595090c15d1
6429796858e4856e0b4b542408a48a25a7fdb454f3062 name=kata-runtime pid=169665 source=runtime
time="2019-04-17T17:41:17.155291155+08:00" level=debug msg="Could not retrieve anything from storage" arch=amd64 command=create container=b0618b3f02321e121f65f005a8099408fdd6b73af0a6e73141
44ecf5dc75a02e name=kata-runtime pid=173988 source=virtcontainers subsystem=kata_agent
time="2019-04-17T17:41:17.155336873+08:00" level=warning msg="load sandbox devices failed" arch=amd64 command=create container=b0618b3f02321e121f65f005a8099408fdd6b73af0a6e7314144ecf5dc75a
02e error="open /run/vc/sbs/b0618b3f02321e121f65f005a8099408fdd6b73af0a6e7314144ecf5dc75a02e/devices.json: no such file or directory" name=kata-runtime pid=173988 sandbox=b0618b3f02321e121
f65f005a8099408fdd6b73af0a6e7314144ecf5dc75a02e sandboxid=b0618b3f02321e121f65f005a8099408fdd6b73af0a6e7314144ecf5dc75a02e source=virtcontainers subsystem=sandbox

## Proxy logs

Recent proxy problems found in system journal:

time="2019-04-10T15:31:02.747544202+08:00" level=info msg="time="2019-04-10T07:31:02.739084201Z" level=info msg="ignoring unexpected signal" name=kata-agent pid=97 sandbox=6456e69ec541
b10a7d04e00d70364490165f9205bdaf27e6829216320047fb47 signal="child exited" source=agent\n" name=kata-proxy pid=103319 sandbox=6456e69ec541b10a7d04e00d70364490165f9205bdaf27e6829216320047
fb47 source=agent
time="2019-04-10T15:31:02.876833586+08:00" level=fatal msg="channel error" error="accept unix /run/vc/sbs/6456e69ec541b10a7d04e00d70364490165f9205bdaf27e6829216320047fb47/proxy.sock: use o
f closed network connection" name=kata-proxy pid=103319 sandbox=6456e69ec541b10a7d04e00d70364490165f9205bdaf27e6829216320047fb47 source=proxy
time="2019-04-10T16:55:28.524929817+08:00" level=info msg="[    0.338048] systemd[73]: tmp.mount: Failed to execute command: No such file or directory\n" name=kata-proxy pid=108738 sandbox
=40037cb4147f224187eed7ace0bfbb382e6ccd33acc5fb0f5b2ab447b6173c77 source=agent
time="2019-04-10T16:55:28.969383688+08:00" level=info msg="time="2019-04-10T08:55:28.96116418Z" level=info msg="ignoring unexpected signal" name=kata-agent pid=100 sandbox=40037cb4147f
224187eed7ace0bfbb382e6ccd33acc5fb0f5b2ab447b6173c77 signal="child exited" source=agent\n" name=kata-proxy pid=108738 sandbox=40037cb4147f224187eed7ace0bfbb382e6ccd33acc5fb0f5b2ab447b617
3c77 source=agent
time="2019-04-10T16:55:28.969525647+08:00" level=info msg="time="2019-04-10T08:55:28.96137286Z" level=info msg="ignoring unexpected signal" name=kata-agent pid=100 sandbox=40037cb4147f
224187eed7ace0bfbb382e6ccd33acc5fb0f5b2ab447b6173c77 signal="child exited" source=agent\n" name=kata-proxy pid=108738 sandbox=40037cb4147f224187eed7ace0bfbb382e6ccd33acc5fb0f5b2ab447b617
3c77 source=agent
time="2019-04-10T16:55:29.899920789+08:00" level=info msg="time="2019-04-10T08:55:29.891775121Z" level=info msg="ignoring unexpected signal" name=kata-agent pid=100 sandbox=40037cb4147
f224187eed7ace0bfbb382e6ccd33acc5fb0f5b2ab447b6173c77 signal="child exited" source=agent\n" name=kata-proxy pid=108738 sandbox=40037cb4147f224187eed7ace0bfbb382e6ccd33acc5fb0f5b2ab447b61
73c77 source=agent
time="2019-04-10T16:55:29.987071929+08:00" level=fatal msg="failed to handle exit signal" error="close unix @->/run/vc/vm/40037cb4147f224187eed7ace0bfbb382e6ccd33acc5fb0f5b2ab447b6173c77/k
ata.sock: use of closed network connection" name=kata-proxy pid=108738 sandbox=40037cb4147f224187eed7ace0bfbb382e6ccd33acc5fb0f5b2ab447b6173c77 source=proxy
time="2019-04-10T17:09:48.228477356+08:00" level=info msg="[    0.331080] systemd[69]: tmp.mount: Failed to execute command: No such file or directory\n" name=kata-proxy pid=109884 sandbox
=7a0027b0aab1f9896da8181f151a4f15d4b148f652763fa5b82579dfafea88f0 source=agent
time="2019-04-10T17:09:48.698428965+08:00" level=info msg="time="2019-04-10T09:09:48.690667899Z" level=info msg="ignoring unexpected signal" name=kata-agent pid=95 sandbox=7a0027b0aab1
f9896da8181f151a4f15d4b148f652763fa5b82579dfafea88f0 signal="child exited" source=agent\n" name=kata-proxy pid=109884 sandbox=7a0027b0aab1f9896da8181f151a4f15d4b148f652763fa5b82579dfafea
88f0 source=agent
time="2019-04-10T17:09:48.698499521+08:00" level=info msg="time="2019-04-10T09:09:48.690901383Z" level=info msg="ignoring unexpected signal" name=kata-agent pid=95 sandbox=7a0027b0aab1
f9896da8181f151a4f15d4b148f652763fa5b82579dfafea88f0 signal="child exited" source=agent\n" name=kata-proxy pid=109884 sandbox=7a0027b0aab1f9896da8181f151a4f15d4b148f652763fa5b82579dfafea
88f0 source=agent
time="2019-04-10T17:09:48.699522008+08:00" level=debug msg="Copy stream error" error="read unix /run/vc/sbs/7a0027b0aab1f9896da8181f151a4f15d4b148f652763fa5b82579dfafea88f0/proxy.sock->@:
read: connection reset by peer" name=kata-proxy pid=109884 sandbox=7a0027b0aab1f9896da8181f151a4f15d4b148f652763fa5b82579dfafea88f0 source=proxy
time="2019-04-10T22:27:21.598428554+08:00" level=info msg="time="2019-04-10T14:27:21.589703056Z" level=info msg="ignoring unexpected signal" name=kata-agent pid=95 sandbox=7a0027b0aab1
f9896da8181f151a4f15d4b148f652763fa5b82579dfafea88f0 signal="child exited" source=agent\n" name=kata-proxy pid=109884 sandbox=7a0027b0aab1f9896da8181f151a4f15d4b148f652763fa5b82579dfafea
88f0 source=agent
time="2019-04-10T22:27:21.600380976+08:00" level=debug msg="Copy stream error" error="write unix /run/vc/sbs/7a0027b0aab1f9896da8181f151a4f15d4b148f652763fa5b82579dfafea88f0/proxy.sock->@:
write: broken pipe" name=kata-proxy pid=109884 sandbox=7a0027b0aab1f9896da8181f151a4f15d4b148f652763fa5b82579dfafea88f0 source=proxy
time="2019-04-10T22:27:21.732280423+08:00" level=fatal msg="channel error" error="accept unix /run/vc/sbs/7a0027b0aab1f9896da8181f151a4f15d4b148f652763fa5b82579dfafea88f0/proxy.sock: use o
f closed network connection" name=kata-proxy pid=109884 sandbox=7a0027b0aab1f9896da8181f151a4f15d4b148f652763fa5b82579dfafea88f0 source=proxy
time="2019-04-10T22:28:01.919382173+08:00" level=info msg="[    0.378555] systemd[78]: tmp.mount: Failed to execute command: No such file or directory\n" name=kata-proxy pid=129799 sandbox
=5af7576b444d7663300dbc50c74b2665ad84ddde0b3e74f8cdafe351c5759ef4 source=agent
time="2019-04-10T22:28:02.404004604+08:00" level=info msg="time="2019-04-10T14:28:02.39414142Z" level=info msg="ignoring unexpected signal" name=kata-agent pid=96 sandbox=5af7576b444d7
663300dbc50c74b2665ad84ddde0b3e74f8cdafe351c5759ef4 signal="child exited" source=agent\n" name=kata-proxy pid=129799 sandbox=5af7576b444d7663300dbc50c74b2665ad84ddde0b3e74f8cdafe351c5759
ef4 source=agent
time="2019-04-10T22:28:02.404200896+08:00" level=info msg="time="2019-04-10T14:28:02.394478279Z" level=info msg="ignoring unexpected signal" name=kata-agent pid=96 sandbox=5af7576b444d
7663300dbc50c74b2665ad84ddde0b3e74f8cdafe351c5759ef4 signal="child exited" source=agent\n" name=kata-proxy pid=129799 sandbox=5af7576b444d7663300dbc50c74b2665ad84ddde0b3e74f8cdafe351c575
9ef4 source=agent
time="2019-04-10T22:28:02.529178492+08:00" level=debug msg="Copy stream error" error="read unix /run/vc/sbs/5af7576b444d7663300dbc50c74b2665ad84ddde0b3e74f8cdafe351c5759ef4/proxy.sock->@:
read: connection reset by peer" name=kata-proxy pid=129799 sandbox=5af7576b444d7663300dbc50c74b2665ad84ddde0b3e74f8cdafe351c5759ef4 source=proxy
time="2019-04-10T22:28:03.279321071+08:00" level=info msg="time="2019-04-10T14:28:03.269653035Z" level=info msg="ignoring unexpected signal" name=kata-agent pid=96 sandbox=5af7576b444d
7663300dbc50c74b2665ad84ddde0b3e74f8cdafe351c5759ef4 signal="child exited" source=agent\n" name=kata-proxy pid=129799 sandbox=5af7576b444d7663300dbc50c74b2665ad84ddde0b3e74f8cdafe351c575
9ef4 source=agent
time="2019-04-10T22:28:03.280975359+08:00" level=debug msg="Copy stream error" error="read unix /run/vc/sbs/5af7576b444d7663300dbc50c74b2665ad84ddde0b3e74f8cdafe351c5759ef4/proxy.sock->@:
read: connection reset by peer" name=kata-proxy pid=129799 sandbox=5af7576b444d7663300dbc50c74b2665ad84ddde0b3e74f8cdafe351c5759ef4 source=proxy
time="2019-04-10T22:28:03.388393597+08:00" level=fatal msg="channel error" error="accept unix /run/vc/sbs/5af7576b444d7663300dbc50c74b2665ad84ddde0b3e74f8cdafe351c5759ef4/proxy.sock: use o
f closed network connection" name=kata-proxy pid=129799 sandbox=5af7576b444d7663300dbc50c74b2665ad84ddde0b3e74f8cdafe351c5759ef4 source=proxy
time="2019-04-15T16:43:58.00227813+08:00" level=info msg="[    0.353248] systemd[72]: tmp.mount: Failed to execute command: No such file or directory\n" name=kata-proxy pid=272076 sandbox=
3122d618a896589702f918616847f014ae48030eba0e7f2df2320284d29c85c2 source=agent
time="2019-04-15T16:43:58.495244558+08:00" level=info msg="time="2019-04-15T08:43:58.485880146Z" level=info msg="ignoring unexpected signal" name=kata-agent pid=97 sandbox=3122d618a896
589702f918616847f014ae48030eba0e7f2df2320284d29c85c2 signal="child exited" source=agent\n" name=kata-proxy pid=272076 sandbox=3122d618a896589702f918616847f014ae48030eba0e7f2df2320284d29c
85c2 source=agent
time="2019-04-15T16:43:58.499142281+08:00" level=info msg="time="2019-04-15T08:43:58.486823321Z" level=info msg="ignoring unexpected signal" name=kata-agent pid=97 sandbox=3122d618a896
589702f918616847f014ae48030eba0e7f2df2320284d29c85c2 signal="child exited" source=agent\n" name=kata-proxy pid=272076 sandbox=3122d618a896589702f918616847f014ae48030eba0e7f2df2320284d29c
85c2 source=agent
time="2019-04-15T16:43:58.644905396+08:00" level=debug msg="Copy stream error" error="read unix /run/vc/sbs/3122d618a896589702f918616847f014ae48030eba0e7f2df2320284d29c85c2/proxy.sock->@:
read: connection reset by peer" name=kata-proxy pid=272076 sandbox=3122d618a896589702f918616847f014ae48030eba0e7f2df2320284d29c85c2 source=proxy
time="2019-04-16T17:07:45.521864015+08:00" level=info msg="[    0.367060] systemd[72]: tmp.mount: Failed to execute command: No such file or directory\n" name=kata-proxy pid=82343 sandbox=
6d4b102a48e19d90eeb1ecc753c2ed246ca8d3f7f4d0840ea888207b1addb6b7 source=agent
time="2019-04-16T17:07:45.927047559+08:00" level=fatal msg="failed to handle exit signal" error="close unix @->/run/vc/vm/6d4b102a48e19d90eeb1ecc753c2ed246ca8d3f7f4d0840ea888207b1addb6b7/k
ata.sock: use of closed network connection" name=kata-proxy pid=82343 sandbox=6d4b102a48e19d90eeb1ecc753c2ed246ca8d3f7f4d0840ea888207b1addb6b7 source=proxy
time="2019-04-16T17:07:59.878318099+08:00" level=info msg="[    0.338545] systemd[73]: tmp.mount: Failed to execute command: No such file or directory\n" name=kata-proxy pid=82441 sandbox=
2b20edf0dc79b902b096386202f8b37caf27f1badfa8085d3384dd251ad75d28 source=agent
time="2019-04-16T17:08:00.269508126+08:00" level=fatal msg="failed to handle exit signal" error="close unix @->/run/vc/vm/2b20edf0dc79b902b096386202f8b37caf27f1badfa8085d3384dd251ad75d28/k
ata.sock: use of closed network connection" name=kata-proxy pid=82441 sandbox=2b20edf0dc79b902b096386202f8b37caf27f1badfa8085d3384dd251ad75d28 source=proxy
time="2019-04-16T17:17:33.624211252+08:00" level=info msg="[    0.356064] systemd[71]: tmp.mount: Failed to execute command: No such file or directory\n" name=kata-proxy pid=83110 sandbox=
37cb8ad988f540887bd9aa44d178c207f4d93f5dd44220c09f0a4356465a9e0d source=agent
time="2019-04-16T17:17:34.021742069+08:00" level=fatal msg="failed to handle exit signal" error="close unix @->/run/vc/vm/37cb8ad988f540887bd9aa44d178c207f4d93f5dd44220c09f0a4356465a9e0d/k
ata.sock: use of closed network connection" name=kata-proxy pid=83110 sandbox=37cb8ad988f540887bd9aa44d178c207f4d93f5dd44220c09f0a4356465a9e0d source=proxy
time="2019-04-16T17:18:21.348444408+08:00" level=info msg="[    0.317085] systemd[71]: tmp.mount: Failed to execute command: No such file or directory\n" name=kata-proxy pid=83227 sandbox=
c727a814256d307b45a49fe7cb4822bffe418037577b968d2f37bef37fb21267 source=agent
time="2019-04-16T17:18:21.711495692+08:00" level=fatal msg="channel error" error="accept unix /run/vc/sbs/c727a814256d307b45a49fe7cb4822bffe418037577b968d2f37bef37fb21267/proxy.sock: use o
f closed network connection" name=kata-proxy pid=83227 sandbox=c727a814256d307b45a49fe7cb4822bffe418037577b968d2f37bef37fb21267 source=proxy
time="2019-04-16T17:22:38.141326232+08:00" level=info msg="time="2019-04-16T09:22:38.127723743Z" level=info msg="ignoring unexpected signal" name=kata-agent pid=97 sandbox=3122d618a896
589702f918616847f014ae48030eba0e7f2df2320284d29c85c2 signal="child exited" source=agent\n" name=kata-proxy pid=272076 sandbox=3122d618a896589702f918616847f014ae48030eba0e7f2df2320284d29c
85c2 source=agent
time="2019-04-16T17:22:38.147641515+08:00" level=debug msg="Copy stream error" error="read unix /run/vc/sbs/3122d618a896589702f918616847f014ae48030eba0e7f2df2320284d29c85c2/proxy.sock->@:
read: connection reset by peer" name=kata-proxy pid=272076 sandbox=3122d618a896589702f918616847f014ae48030eba0e7f2df2320284d29c85c2 source=proxy
time="2019-04-16T17:22:38.280308978+08:00" level=fatal msg="failed to handle exit signal" error="close unix @->/run/vc/vm/3122d618a896589702f918616847f014ae48030eba0e7f2df2320284d29c85c2/k
ata.sock: use of closed network connection" name=kata-proxy pid=272076 sandbox=3122d618a896589702f918616847f014ae48030eba0e7f2df2320284d29c85c2 source=proxy
time="2019-04-16T17:23:15.113981787+08:00" level=info msg="[    0.543932] systemd[75]: tmp.mount: Failed to execute command: No such file or directory\n" name=kata-proxy pid=83847 sandbox=
d4c091664726ad991659f8e28e8e238b931e9f95a303cb6c3901eac4e389fcd6 source=agent
time="2019-04-16T17:23:15.627971406+08:00" level=fatal msg="channel error" error="accept unix /run/vc/sbs/d4c091664726ad991659f8e28e8e238b931e9f95a303cb6c3901eac4e389fcd6/proxy.sock: use o
f closed network connection" name=kata-proxy pid=83847 sandbox=d4c091664726ad991659f8e28e8e238b931e9f95a303cb6c3901eac4e389fcd6 source=proxy
time="2019-04-17T15:52:12.664205393+08:00" level=info msg="[    0.585070] systemd[82]: tmp.mount: Failed to execute command: No such file or directory\n" name=kata-proxy pid=166876 sandbox
=d2e84d608f77a85c98f1d37115254a6e0b769b020ee111455a1412d92b45904b source=agent
time="2019-04-17T15:52:13.13977264+08:00" level=fatal msg="channel error" error="accept unix /run/vc/sbs/d2e84d608f77a85c98f1d37115254a6e0b769b020ee111455a1412d92b45904b/proxy.sock: use of
closed network connection" name=kata-proxy pid=166876 sandbox=d2e84d608f77a85c98f1d37115254a6e0b769b020ee111455a1412d92b45904b source=proxy
time="2019-04-17T16:34:44.696314399+08:00" level=info msg="[    0.545928] systemd[76]: tmp.mount: Failed to execute command: No such file or directory\n" name=kata-proxy pid=169606 sandbox
=a98c2d8a7bb80dca033eca387ba837754f55316876411dae7e4c0fad1600021b source=agent
time="2019-04-17T16:34:45.186585631+08:00" level=debug msg="Copy stream error" error="read unix /run/vc/sbs/a98c2d8a7bb80dca033eca387ba837754f55316876411dae7e4c0fad1600021b/proxy.sock->@:
use of closed network connection" name=kata-proxy pid=169606 sandbox=a98c2d8a7bb80dca033eca387ba837754f55316876411dae7e4c0fad1600021b source=proxy
time="2019-04-17T16:34:45.186593065+08:00" level=fatal msg="failed to handle exit signal" error="close unix @->/run/vc/vm/a98c2d8a7bb80dca033eca387ba837754f55316876411dae7e4c0fad1600021b/k
ata.sock: use of closed network connection" name=kata-proxy pid=169606 sandbox=a98c2d8a7bb80dca033eca387ba837754f55316876411dae7e4c0fad1600021b source=proxy
time="2019-04-17T16:35:08.412348611+08:00" level=info msg="[    0.527783] systemd[75]: tmp.mount: Failed to execute command: No such file or directory\n" name=kata-proxy pid=169702 sandbox
=5b3633d8595090c15d16429796858e4856e0b4b542408a48a25a7fdb454f3062 source=agent
time="2019-04-17T16:35:08.927530209+08:00" level=fatal msg="failed to handle exit signal" error="close unix @->/run/vc/vm/5b3633d8595090c15d16429796858e4856e0b4b542408a48a25a7fdb454f3062/k
ata.sock: use of closed network connection" name=kata-proxy pid=169702 sandbox=5b3633d8595090c15d16429796858e4856e0b4b542408a48a25a7fdb454f3062 source=proxy
time="2019-04-17T17:41:18.014469476+08:00" level=info msg="[    0.349249] systemd[73]: tmp.mount: Failed to execute command: No such file or directory\n" name=kata-proxy pid=174026 sandbox
=b0618b3f02321e121f65f005a8099408fdd6b73af0a6e7314144ecf5dc75a02e source=agent
time="2019-04-17T17:41:18.469755612+08:00" level=info msg="time="2019-04-17T09:41:18.462272003Z" level=info msg="ignoring unexpected signal" name=kata-agent pid=108 sandbox=b0618b3f023
21e121f65f005a8099408fdd6b73af0a6e7314144ecf5dc75a02e signal="child exited" source=agent\n" name=kata-proxy pid=174026 sandbox=b0618b3f02321e121f65f005a8099408fdd6b73af0a6e7314144ecf5dc7
5a02e source=agent
time="2019-04-17T17:41:18.469915366+08:00" level=info msg="time="2019-04-17T09:41:18.462491794Z" level=info msg="ignoring unexpected signal" name=kata-agent pid=108 sandbox=b0618b3f023
21e121f65f005a8099408fdd6b73af0a6e7314144ecf5dc75a02e signal="child exited" source=agent\n" name=kata-proxy pid=174026 sandbox=b0618b3f02321e121f65f005a8099408fdd6b73af0a6e7314144ecf5dc7
5a02e source=agent
time="2019-04-17T17:41:18.60879889+08:00" level=info msg="time="2019-04-17T09:41:18.601252407Z" level=info msg="ignoring unexpected signal" name=kata-agent pid=108 sandbox=b0618b3f0232
1e121f65f005a8099408fdd6b73af0a6e7314144ecf5dc75a02e signal="child exited" source=agent\n" name=kata-proxy pid=174026 sandbox=b0618b3f02321e121f65f005a8099408fdd6b73af0a6e7314144ecf5dc75
a02e source=agent
time="2019-04-17T17:41:18.720054909+08:00" level=fatal msg="failed to handle exit signal" error="close unix @->/run/vc/vm/b0618b3f02321e121f65f005a8099408fdd6b73af0a6e7314144ecf5dc75a02e/k
ata.sock: use of closed network connection" name=kata-proxy pid=174026 sandbox=b0618b3f02321e121f65f005a8099408fdd6b73af0a6e7314144ecf5dc75a02e source=proxy

## Shim logs

Recent shim problems found in system journal:

time="2019-04-09T10:58:57.469193961+08:00" level=info msg="copy stdout failed" container=c215edafcbba900ab77412b5a074529afd7cfd92a88a75c4c0a3586d3f9c266f error="rpc error: code = Unknown d
esc = read /dev/ptmx: input/output error" exec-id=c215edafcbba900ab77412b5a074529afd7cfd92a88a75c4c0a3586d3f9c266f name=kata-shim pid=1 source=shim
time="2019-04-10T15:31:02.74639583+08:00" level=info msg="copy stdout failed" container=6456e69ec541b10a7d04e00d70364490165f9205bdaf27e6829216320047fb47 error="rpc error: code = Unknown de
sc = read /dev/ptmx: input/output error" exec-id=6456e69ec541b10a7d04e00d70364490165f9205bdaf27e6829216320047fb47 name=kata-shim pid=1 source=shim
time="2019-04-10T16:55:29.898108347+08:00" level=info msg="copy stdout failed" container=40037cb4147f224187eed7ace0bfbb382e6ccd33acc5fb0f5b2ab447b6173c77 error="rpc error: code = Unknown d
esc = read /dev/ptmx: input/output error" exec-id=40037cb4147f224187eed7ace0bfbb382e6ccd33acc5fb0f5b2ab447b6173c77 name=kata-shim pid=1 source=shim
time="2019-04-10T22:27:21.596785617+08:00" level=info msg="copy stdout failed" container=7a0027b0aab1f9896da8181f151a4f15d4b148f652763fa5b82579dfafea88f0 error="rpc error: code = Unknown d
esc = read /dev/ptmx: input/output error" exec-id=7a0027b0aab1f9896da8181f151a4f15d4b148f652763fa5b82579dfafea88f0 name=kata-shim pid=1 source=shim
time="2019-04-10T22:28:03.277721921+08:00" level=info msg="copy stdout failed" container=5af7576b444d7663300dbc50c74b2665ad84ddde0b3e74f8cdafe351c5759ef4 error="rpc error: code = Unknown d
esc = read /dev/ptmx: input/output error" exec-id=5af7576b444d7663300dbc50c74b2665ad84ddde0b3e74f8cdafe351c5759ef4 name=kata-shim pid=1 source=shim
time="2019-04-16T17:22:38.137872318+08:00" level=info msg="copy stdout failed" container=3122d618a896589702f918616847f014ae48030eba0e7f2df2320284d29c85c2 error="rpc error: code = Unknown d
esc = read /dev/ptmx: input/output error" exec-id=3122d618a896589702f918616847f014ae48030eba0e7f2df2320284d29c85c2 name=kata-shim pid=1 source=shim
time="2019-04-17T17:41:18.611470323+08:00" level=info msg="copy stdout failed" container=b0618b3f02321e121f65f005a8099408fdd6b73af0a6e7314144ecf5dc75a02e error="rpc error: code = Unknown d
esc = read /dev/ptmx: input/output error" exec-id=b0618b3f02321e121f65f005a8099408fdd6b73af0a6e7314144ecf5dc75a02e name=kata-shim pid=1 source=shim

## Throttler logs

No recent throttler problems found in system journal.

---

# Container manager details

Have `docker`

## Docker

Output of "`docker version`":

Client:
Version:           18.06.2-ce
API version:       1.38
Go version:        go1.10.3
Git commit:        6d37f41
Built:             Sun Feb 10 03:46:03 2019
OS/Arch:           linux/amd64
Experimental:      false
Server:
Engine:
Version:          18.06.2-ce
API version:      1.38 (minimum version 1.12)
Go version:       go1.10.3
Git commit:       6d37f41
Built:            Sun Feb 10 03:48:29 2019
OS/Arch:          linux/amd64
Experimental:     false
Output of "`docker info`":

Containers: 14
Running: 0
Paused: 0
Stopped: 14
Images: 9
Server Version: 18.06.2-ce
Storage Driver: overlay2
Backing Filesystem: extfs
Supports d_type: true
Native Overlay Diff: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
Volume: local
Network: bridge host macvlan null overlay
Log: awslogs fluentd gcplogs gelf journald json-file logentries splunk syslog
Swarm: inactive
Runtimes: kata-runtime runc
Default Runtime: kata-runtime
Init Binary: docker-init
containerd version: 468a545b9edcd5932818eb9de8e72413e616e86e
runc version: 9f8d4e1 (expected: 69663f0bd4b60df09991c08812a60108003fa340)
init version: fec3683
Security Options:
seccomp
Profile: default
Kernel Version: 3.10.0-862.el7.x86_64
Operating System: CentOS Linux 7 (Core)
OSType: linux
Architecture: x86_64
CPUs: 4
Total Memory: 7.639GiB
Name: centos-k8s014.sh.intel.com
ID: GL32:HRHJ:IVSY:WKDP:UZ2S:FMVO:HP6B:A5KV:X7T6:DBBU:VT26:X6RP
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): true
File Descriptors: 22
Goroutines: 44
System Time: 2019-04-17T17:43:20.205014289+08:00
EventsListeners: 0
HTTP Proxy: http://child-prc.intel.com:913/
Registry: https://index.docker.io/v1/
Labels:
Experimental: false
Insecure Registries:
127.0.0.0/8
Live Restore Enabled: false
Output of "`systemctl show docker`":

Type=notify
Restart=on-failure
NotifyAccess=main
RestartUSec=100ms
TimeoutStartUSec=0
TimeoutStopUSec=1min 30s
WatchdogUSec=0
WatchdogTimestamp=Wed 2019-04-17 17:40:25 CST
WatchdogTimestampMonotonic=2534654669193
StartLimitInterval=60000000
StartLimitBurst=3
StartLimitAction=none
FailureAction=none
PermissionsStartOnly=no
RootDirectoryStartOnly=no
RemainAfterExit=no
GuessMainPID=yes
MainPID=173758
ControlPID=0
FileDescriptorStoreMax=0
StatusErrno=0
Result=success
ExecMainStartTimestamp=Wed 2019-04-17 17:40:25 CST
ExecMainStartTimestampMonotonic=2534654295380
ExecMainExitTimestampMonotonic=0
ExecMainPID=173758
ExecMainCode=0
ExecMainStatus=0
ExecStart={ path=/usr/bin/dockerd ; argv[]=/usr/bin/dockerd -D --add-runtime kata-runtime=/usr/bin/kata-runtime --default-runtime=kata-runtime ; ignore_errors=no ; start_time=[Wed 2019-04-
17 17:40:25 CST] ; stop_time=[n/a] ; pid=173758 ; code=(null) ; status=0/0 }
ExecReload={ path=/bin/kill ; argv[]=/bin/kill -s HUP $MAINPID ; ignore_errors=no ; start_time=[n/a] ; stop_time=[n/a] ; pid=0 ; code=(null) ; status=0/0 }
Slice=system.slice
ControlGroup=/system.slice/docker.service
MemoryCurrent=181837824
TasksCurrent=53
Delegate=yes
CPUAccounting=no
CPUShares=18446744073709551615
StartupCPUShares=18446744073709551615
CPUQuotaPerSecUSec=infinity
BlockIOAccounting=no
BlockIOWeight=18446744073709551615
StartupBlockIOWeight=18446744073709551615
MemoryAccounting=no
MemoryLimit=18446744073709551615
DevicePolicy=auto
TasksAccounting=no
TasksMax=18446744073709551615
Environment=HTTP_PROXY=http://child-prc.intel.com:913/
UMask=0022
LimitCPU=18446744073709551615
LimitFSIZE=18446744073709551615
LimitDATA=18446744073709551615
LimitSTACK=18446744073709551615
LimitCORE=18446744073709551615
LimitRSS=18446744073709551615
LimitNOFILE=18446744073709551615
LimitAS=18446744073709551615
LimitNPROC=18446744073709551615
LimitMEMLOCK=65536
LimitLOCKS=18446744073709551615
LimitSIGPENDING=31165
LimitMSGQUEUE=819200
LimitNICE=0
LimitRTPRIO=0
LimitRTTIME=18446744073709551615
OOMScoreAdjust=0
Nice=0
IOScheduling=0
CPUSchedulingPolicy=0
CPUSchedulingPriority=0
TimerSlackNSec=50000
CPUSchedulingResetOnFork=no
NonBlocking=no
StandardInput=null
StandardOutput=journal
StandardError=inherit
TTYReset=no
TTYVHangup=no
TTYVTDisallocate=no
SyslogPriority=30
SyslogLevelPrefix=yes
SecureBits=0
CapabilityBoundingSet=18446744073709551615
AmbientCapabilities=0
MountFlags=0
PrivateTmp=no
PrivateNetwork=no
PrivateDevices=no
ProtectHome=no
ProtectSystem=no
SameProcessGroup=no
IgnoreSIGPIPE=yes
NoNewPrivileges=no
SystemCallErrorNumber=0
RuntimeDirectoryMode=0755
KillMode=process
KillSignal=15
SendSIGKILL=yes
SendSIGHUP=no
Id=docker.service
Names=docker.service
Requires=basic.target
Wants=system.slice network-online.target
Conflicts=shutdown.target
Before=shutdown.target
After=network-online.target firewalld.service systemd-journald.socket system.slice basic.target
Documentation=https://docs.docker.com
Description=Docker Application Container Engine
LoadState=loaded
ActiveState=active
SubState=running
FragmentPath=/usr/lib/systemd/system/docker.service
DropInPaths=/etc/systemd/system/docker.service.d/kata-container.conf
UnitFileState=disabled
UnitFilePreset=disabled
InactiveExitTimestamp=Wed 2019-04-17 17:40:25 CST
InactiveExitTimestampMonotonic=2534654295426
ActiveEnterTimestamp=Wed 2019-04-17 17:40:25 CST
ActiveEnterTimestampMonotonic=2534654669240
ActiveExitTimestamp=Wed 2019-04-17 17:40:24 CST
ActiveExitTimestampMonotonic=2534653287397
InactiveEnterTimestamp=Wed 2019-04-17 17:40:25 CST
InactiveEnterTimestampMonotonic=2534654294093
CanStart=yes
CanStop=yes
CanReload=yes
CanIsolate=no
StopWhenUnneeded=no
RefuseManualStart=no
RefuseManualStop=no
AllowIsolate=no
DefaultDependencies=yes
OnFailureJobMode=replace
IgnoreOnIsolate=no
IgnoreOnSnapshot=no
NeedDaemonReload=no
JobTimeoutUSec=0
JobTimeoutAction=none
ConditionResult=yes
AssertResult=yes
ConditionTimestamp=Wed 2019-04-17 17:40:25 CST
ConditionTimestampMonotonic=2534654294509
AssertTimestamp=Wed 2019-04-17 17:40:25 CST
AssertTimestampMonotonic=2534654294509
Transient=no
No `kubectl`

---

# Packages

No `dpkg`
Have `rpm`
Output of "`rpm -qa|egrep "(cc-oci-runtimecc-runtimerunv|kata-proxy|kata-runtime|kata-shim|kata-ksm-throttler|kata-containers-image|linux-container|qemu-)"`":

qemu-lite-data-2.11.0+git.87517afd72-21.1.x86_64
kata-proxy-bin-1.6.0~rc1+git.2085829-18.1.x86_64
kata-ksm-throttler-1.6.0~rc1.git+ce5b765-20.1.x86_64
qemu-lite-bin-2.11.0+git.87517afd72-21.1.x86_64
kata-containers-image-1.6.0~rc1-17.1.x86_64
qemu-vanilla-2.11.2+git.0982a56a55-21.1.x86_64
qemu-kvm-1.5.3-156.el7.x86_64
kata-runtime-1.6.0~rc1+git.9f8d4e1-26.1.x86_64
libvirt-daemon-driver-qemu-3.9.0-14.el7.x86_64
qemu-vanilla-bin-2.11.2+git.0982a56a55-21.1.x86_64
kata-linux-container-4.19.24.25-20.1.x86_64
qemu-system-x86-2.0.0-1.el7.6.x86_64
qemu-img-1.5.3-156.el7.x86_64
qemu-kvm-common-1.5.3-156.el7.x86_64
kata-shim-1.6.0~rc1+git.0f41347-16.1.x86_64
qemu-guest-agent-2.8.0-2.el7.x86_64
kata-shim-bin-1.6.0~rc1+git.0f41347-16.1.x86_64
ipxe-roms-qemu-20170123-1.git4e85b27.el7_4.1.noarch
kata-proxy-1.6.0~rc1+git.2085829-18.1.x86_64
qemu-vanilla-data-2.11.2+git.0982a56a55-21.1.x86_64
qemu-lite-2.11.0+git.87517afd72-21.1.x86_64
qemu-common-2.0.0-1.el7.6.x86_64

---

@zhiminghufighting this error here looks similar to the one in #1551.
Can you give this a try with the fix I mentioned there.

@amshinde Yes. the fix for '--privileged' works for this issue. Thanks!

authors: amshinde zhiminghufighting

repo: kata-containers/runtime