I'm having a test failure with my GitHub Action where I'm running this command against my kustomization.yaml file:
Run kubeval
ERR - plant-simulator-deployment/templates/base/kustomization.yaml: Failed initalizing schema https://kubernetesjsonschema.dev/master-standalone-strict/kustomization-kustomize-v1beta1.json: Could not read schema from HTTP, response status is 404 Not Found
ERR - plant-simulator-deployment/templates/dev/kustomization.yaml: Failed initalizing schema https://kubernetesjsonschema.dev/master-standalone-strict/kustomization-kustomize-v1beta1.json: Could not read schema from HTTP, response status is 404 Not Found
ERR - plant-simulator-deployment/templates/production/kustomization.yaml: Failed initalizing schema https://kubernetesjsonschema.dev/master-standalone-strict/kustomization-kustomize-v1beta1.json: Could not read schema from HTTP, response status is 404 Not Found
Here is what I have in my kustomization.yaml file:
apiVersion: kustomize.config.k8s.io/v1beta1
Any ideas how to get rid of this error?
You need to pass some options to kubeval to ignore custom resources.
Either ignoring them all with --ignore-missing-schemas or listing the ones to ignore with --skip-kinds
From the official doc
Related
I am following this tutorial https://www.youtube.com/watch?v=I1cG1FRjFOQ and it uses the password from the registry in Azure to login. However, when I try to login running the command docker login epregistry.azurecr.io it gives me the following error Error response from daemon: Get "https://epregistry.azurecr.io/v2/": error parsing HTTP 403 response body: unexpected end of JSON input: "". Can someone please help me?
I think this ACR login server doesn't exist or has been deleted.
I reproduced with my ACR and can log in correctly.
So after I deleted ACR and tried to log in again, I got the same error. (But it is HTTP 404)
Error response from daemon: Get "https://<My-ACR>.azurecr.io": error parsing HTTP 404 response body: unexpected end of JSON input: ""
I am getting an error code in my dev tools.
Error handling response: Error: Failed to construct 'WebSocket': The URL 'ws/ws' is invalid.
at init (chrome-extension://fiegdmejfepffgpnejdinekhfieaogmj/reload.js:22:18)
at chrome-extension://fiegdmejfepffgpnejdinekhfieaogmj/reload.js:65:13
What does this mean and how do I fix it?
I had the same problem and like Aleksey Razbakov said, it's probably from one of your extensions. In my case I had to disabled : Live Server Web Extension. And now this error is gone.
I'm trying to build Yocto for Raspberry Pi3, with console-image, and it gives me some build errors, most I have been able to resolve with
bitbake -c cleansstate libname
bitbake libname
However, now it got to libtalloc and it can't do_fetch the source files.
I went to the URL of the sources, and I was able to download the exact tar.gz archive it was trying to fetch. i.e. http://samba.org/ftp/talloc/talloc-2.1.8.tar.gz
I even put it into /build/downloads folder.
But when I try to bitbake, it keeps giving me the same errors
Is there a way I can configure the build process to always fetch with http or wget, it seems that the these scripts are all broken, because it cant fetch a file that exists.
Thanks,
Here is the full printout:
WARNING: libtalloc-2.1.8-r0 do_fetch: Failed to fetch URL http://samba.org/ftp/talloc/talloc-2.1.8.tar.gz, attempting MIRRORS if available
ERROR: libtalloc-2.1.8-r0 do_fetch: Fetcher failure: Fetch command export DBUS_SESSION_BUS_ADDRESS="unix:abstract=/tmp/dbus-ATqIt180d4"; export SSH_AUTH_SOCK="/run/user/1000/keyring-Ubo22d/ssh"; export PATH="/home/dmitry/rpi/build/tmp/sysroots-uninative/x86_64-linux/usr/bin:/home/dmitry/rpi/build/tmp/sysroots/x86_64-linux/usr/bin/python-native:/home/dmitry/poky-morty/scripts:/home/dmitry/rpi/build/tmp/sysroots/x86_64-linux/usr/bin/arm-poky-linux-gnueabi:/home/dmitry/rpi/build/tmp/sysroots/raspberrypi2/usr/bin/crossscripts:/home/dmitry/rpi/build/tmp/sysroots/x86_64-linux/usr/sbin:/home/dmitry/rpi/build/tmp/sysroots/x86_64-linux/usr/bin:/home/dmitry/rpi/build/tmp/sysroots/x86_64-linux/sbin:/home/dmitry/rpi/build/tmp/sysroots/x86_64-linux/bin:/home/dmitry/poky-morty/scripts:/home/dmitry/poky-morty/bitbake/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games"; export HOME="/home/dmitry"; /usr/bin/env wget -t 2 -T 30 -nv --passive-ftp --no-check-certificate -P /home/dmitry/rpi/build/downloads 'http://samba.org/ftp/talloc/talloc-2.1.8.tar.gz' --progress=dot -v failed with exit code 4, output:
--2017-01-24 12:35:19-- http://samba.org/ftp/talloc/talloc-2.1.8.tar.gz
Resolving samba.org (samba.org)... 144.76.82.156, 2a01:4f8:192:486::443:2
Connecting to samba.org (samba.org)|144.76.82.156|:80... connected.
HTTP request sent, awaiting response... Read error (Connection reset by peer) in headers.
Retrying.
--2017-01-24 12:35:20-- (try: 2) http://samba.org/ftp/talloc/talloc-2.1.8.tar.gz
Connecting to samba.org (samba.org)|144.76.82.156|:80... connected.
HTTP request sent, awaiting response... Read error (Connection reset by peer) in headers.
Giving up.
ERROR: libtalloc-2.1.8-r0 do_fetch: Fetcher failure for URL: 'http://samba.org/ftp/talloc/talloc-2.1.8.tar.gz'. Unable to fetch URL from any source.
ERROR: libtalloc-2.1.8-r0 do_fetch: Function failed: base_do_fetch
ERROR: Logfile of failure stored in: /home/dmitry/rpi/build/tmp/work/cortexa7hf-neon-vfpv4-poky-linux-gnueabi/libtalloc/2.1.8-r0/temp/log.do_fetch.80102
ERROR: Task (/home/dmitry/poky-morty/meta-openembedded/meta-networking/recipes-support/libtalloc/libtalloc_2.1.8.bb:do_fetch) failed with exit code '1'
Is there a way I can configure the build process to always fetch with http or wget, it seems that the these scripts are all broken, because it cant fetch a file that exists.
The scripts already use both wget and http. They're also not really broken, the people maintaining the samba download servers just changed several things in the past week: I believe the libtalloc recipes main SRC_URI just needs to be changed to https://download.samba.org/pub/talloc/talloc-${PV}.tar.gz (the current canonical samba download server).
I'm sure meta-oe maintainer would appreciate a patch if this is indeed the case.
I applied the following patch to meta-openembedded and got it built. There are several samba links already broken.
http://pastebin.com/0uTnAY4g
Regards,
M.
I'm trying to deploy my simple ReactJS project on Google App Engine. But I don't know why deployment is failed on Google App Engine regarding following documentation of Google. https://cloud.google.com/nodejs/getting-started/hello-world
Error logs when I encountered.
The push refers to a repository [us.gcr.io/react-ppshein/appengine/default.20160905t090720] (len: 1)
ec870881572a: Preparing
Post https://us.gcr.io/v2/react-ppshein/appengine/default.20160905t090720/blobs/uploads/: token auth attempt for registry: https://us.gcr.io/v2/token?account=_token&scope=repository%3Areact-ppshein%2Fappengine%2Fdefault.20160905t090720%3Apush%2Cpull&service=us.gcr.io request failed with status: 403 Forbidden
ERROR
ERROR: error pushing image "us.gcr.io/react-ppshein/appengine/default.20160905t090720:latest": exit status 1
ERROR: (gcloud.app.deploy) Error Response: [2] Build failed; check build logs for details
I'm trying to host and distribute xbmc addon on my site. I've made a repository which points to the directory where the addon zip file is. At the same folder I have an xml which describes the addon and so the addon name and description are being recognized by xbmc.
However when trying to install the addon it shows 0% downloading progress and then the progress disappears - resulting in the following error inside xbmc.log file:
ERROR: CCurlFile::FillBuffer - Failed: HTTP response code said error(22)
according to curl errors page, this happens when -
CURLE_HTTP_RETURNED_ERROR (22)
This is returned if CURLOPT_FAILONERROR is set TRUE and the HTTP
server returns an error code that is >= 400.
by that I assume the error may be caused by a misconfigured access permissions (perhaps I need to change some htaccess configuration?).
please help
I solved this on my own eventually. Apparently, the file structure was wrong - I needed to follow the file structure as mentioned in section 4.3 here in order for it to work