I installed (Fresh) PGO following this document : https://access.crunchydata.com/documentation/postgres-operator/v5/installation/helm/
it got deployed but the pod is in "ImagePullBackOff" state.
and "https://registry.developers.crunchydata.com/crunchydata/" is not accessible (404), saying that "This container version is no longer available".
I think the images can be found here: https://hub.docker.com/u/crunchydata
I just tried to install PGO following your link and don't have any issue. What do you have when you execute: docker pull registry.developers.crunchydata.com/crunchydata/crunchy-postgres:centos8-14.1-0 from a worker node in your cluster if your container runtime is docker .
Related
Is it possible to use fscrawler in ubuntu? I have used on windows and it works fine. When I try to follow the same implementation on ubuntu I am getting all kind of errors.
First I just tried to pull the docker image and run it according to this guide https://fscrawler.readthedocs.io/en/latest/installation.html#installation and getting the image with docker pull dadoonet/fscrawler
When I tried to run it with docker run -it --rm -v /home/index:/root/.fscrawler -v /home/messages:/tmp/es:ro dadoonet/fscrawler fscrawler job_name I got this error
/usr/bin/fscrawler: 47: /usr/bin/fscrawler: ps: not found
ERROR StatusLogger Reconfiguration failed: No configuration found for '4e0e2f2a' at 'null' in 'null'
After that I tried to fllow this tutorial fscrawler tutorial to install it and use it in linux. Idownloaded the fscrawler-es7-2.8-SNAPSHOT version, but running bin/fscrawler resumes in the folder where I unzipped the files just gave me this error bin/fscrawler: command not found
Is there any way to use fscrawler in a linux system?
It's a bug on Docker. (https://github.com/dadoonet/fscrawler/issues/1229)
If you install it manually (install the JVM and FSCrawler) it should work well.
I'm attempting to learn how to create a Laravel Docker image by following a tutorial on DigitalOcean using WSL. Following the instructions on the Docker Hub page, however, yields an error:
❯ docker run --rm --interactive --tty -v $(pwd):/app composer install
Loading composer repositories with package information
Updating dependencies (including require-dev)
Package operations: 94 installs, 0 updates, 0 removals
- Installing voku/portable-ascii (1.4.10): Failed to download voku/portable-ascii from dist: Could not delete /app/vendor/voku/portable-ascii/src/voku/helper:
Now trying to download from source
- Installing voku/portable-ascii (1.4.10):
[RuntimeException]
Could not delete /app/vendor/voku/portable-ascii/src/voku/helper:
install [--prefer-source] [--prefer-dist] [--dry-run] [--dev] [--no-dev] [--no-custom-installers] [--no-autoloader] [--no-scripts] [--no-progress] [--no-suggest] [-v|vv|vvv|--verbose] [-o|--optimize-autoloader] [-a|--classmap-authoritative] [--apcu-autoloader] [--ignore-platform-reqs] [--] [<packages>]...
How can I diagnose what I'm doing wrong?
It turns out that the underlying problem had nothing to do with Docker at all. In fact, Composer was trying to tell me what the problem was all along, but I dismissed it as just a symptom of a deeper issue:
[RuntimeException]
Could not delete /app/vendor/voku/portable-ascii/src/voku/helper:
This message was the crux of it all. I noticed that the directory mentioned, [...]/helper, was empty, so I tried to remove it by hand with rmdir. Instead, I got a No such file or directory error message. I attempted many other was to kill this directory, the entire project directory with rm -rf ~/laravel-app from the home folder, etc. Nothing worked.
Some digging around on the internet suggested that it could be an NTFS corruption if I was running into this issue on Windows. Since I am, indeed, attempting this on WSL (Windows Subsystem for Linux), I gave their suggested fix a try: running chkdsk /F in CMD/PowerShell. A reboot was necessary to complete this task, but after getting everything back up and trying those first few tutorial steps again, I was able to get composer to install the Laravel dependencies without a hitch.
Bottom line: If you run into this sort of issue on WSL, please try running chkdsk /F and reboot. You might just have a similar file system corruption.
We have two possibilities for this error:
1 - You did not execute the command inside the directory :
cd ~/laravel-app
2 - I'm sure there is an internal proxy that is blocking the download of packages.
I'm getting the same error as mentioned here, but the error only happens on the automated docker hub build, not when running the Dockerfile locally. I've tried all the solutions mentioned with no success.
It was an issue related the most recent build. I fixed it by adding
RUN npm uninstall ajv
RUN npm install ajv#6.8.1
to the dockerfile. This should not longer be an issue for anyone or you are using the wrong version of ajv.
I'm trying to get the CircleCI CLI tool ( https://circleci.com/docs/2.0/local-jobs/ ) working on Ubuntu WSL on Windows 10. It appeared to install successfully -- and the file permissions appear to be correct. I have Docker for Windows installed and running, and the Linux Docker client works without issue.
But now it always errors when trying to validate a CircleCI config file.
I have tried:
circleci config validate -c .circleci/config.yml
and
circleci config validate
from the root of my repo.
But each time, it gives the error:
Error: open .circleci/config.yml: no such file or directory
Has anyone been able to get this work?
sudo worked for me to overcome this. However, I stuck with the next error.
I've installed Docker following exactly the documentation on the website but when I try to run docker run hello-world, I get the following output from the terminal:
Saved file tree to doc-filelist.js
Copied JS to doc-script.js
Compiled CSS to doc-style.css
Does anybody have an idea what is going wrong?
Is it possible that you have docker.js installed locally?
The output from your command looks like the docker.js docker executable is called instead of the Docker container one.
The log messages that you showed can be found in the docker.js documentation, it looks like you're running that instead of the one you want.
If this is the issue run npm uninstall -g docker
I was experiencing the same issue, and it turned out to be caused by running nvm (node version manager). When I used nvm to run Node, Docker was not recognized. However, when I removed nvm, Docker worked as expected. I'm sure there's a workaround to make nvm and Docker work together, and I'll look into that later so I can continue using both tools.