centerforopenscience / docker-library Goto Github PK

Is there a quay.io container that contains only the OSF CLI client? The only one I see that seems to have it is the general all-things-OSF container quay.io/centerforopenscience/osf.

hi

you seem to have two parallel implementations

one in Docker, the other in Ansible?

I dont see any interaction or inter-dependencies

whats the best approach? or what way is COS leaning?

The image built by this Dockerfile is 3 years old and and has a high-level vulnerability that has been patched in a newer version. For its base image, it uses a version of Alpine that reached end-of-support over a year ago.

$ date
Mon Dec 14 17:06:32 PST 2020
$ docker run --rm -ti quay.io/centerforopenscience/pgbouncer:1.8.1 sh
Unable to find image 'quay.io/centerforopenscience/pgbouncer:1.8.1' locally
1.8.1: Pulling from centerforopenscience/pgbouncer
2fdfe1cd78c2: Pull complete
c793e0056529: Pull complete
6bae82978a32: Pull complete
Digest: sha256:fa5c09bf5c39539492f8db53ff66eeb6354a6e41eea101baecbadf88897c76b3
Status: Downloaded newer image for quay.io/centerforopenscience/pgbouncer:1.8.1
/ # cat /etc/os-release
NAME="Alpine Linux"
ID=alpine
VERSION_ID=3.7.0
PRETTY_NAME="Alpine Linux v3.7"
HOME_URL="http://alpinelinux.org"
BUG_REPORT_URL="http://bugs.alpinelinux.org"

It's old enough that security scanners are just saying 🤷‍♂️ or "The vulnerability detection may be insufficient because security updates are not provided".

Hi,
I am Kang Yin, a graduate student of Institute of Software, Chinese Academy of Sciences. Now we are doing a research on how to recommend tags for Docker Hub’s projects. We applied text mining and natural language processing to build a tag recommendation system for Docker projects.
We notice that you have created a repository on Docker Hub, which is named centerforopenscience/apt-cacher and the project address is https://hub.docker.com/r/centerforopenscience/apt-cacher/
Since the developers knows their projects better, we want to evaluate our recommendation results with your help as the project developer. We want to know if the recommended tags are reasonable for your projects.
The following tags (ranked by order) are generated from our model automatically. Would you like to do me a favor and reply with what tags are reasonable (Good) and what are not (Bad), in form of, “Good tags: ***, ***; Bad tags: ***, ***”.

The recommend tags for your project centerforopenscience/apt-cacher are listed as follows:

cacher, apt-cacher, apt, centerforopenscience, caching, packages

It will be a great help if you can give us a feedback.
Thank you so much for your precious time.

Hey,
I downloaded and started the CAS Docker file, but the Docker container just throw exceptions that they can’t connect to Postgresql at 127.0.0.1:5432 and to the mongodb at 127.0.0.1:27017. I don’t know with Postgresql Database they are looking and the mongodb is running at 127.0.0.1:27017. At the end I got the message Started ServerConnector@(…) {0.0.0.0:8080}, but if I look at the Netstat there is no service listening on Port 8080. I would be grateful for some support on that.

Hi, i just cloned it and done docker-compose up -d from the cas folder, now when i visited to url https://localhost:8433 the below shown error appearing any help.

Hello,

Please add a link to this repo (https://github.com/CenterForOpenScience/docker-library/) in the descriptions of each OSF container on quay.io (https://quay.io/repository/centerforopenscience). It is not easy to find this repository from quay.io.

The unoconv image fails to run because the path to the unoconv binary is incorrect, should be /usr/local/bin/unoconv.

$ docker run centerforopenscience/unoconv:latest
/opt/libreoffice6.0/program/python.bin: can't open file '/usr/bin/unoconv': [Errno 2] No such file or directory

The plugin is released.
https://github.com/fabric8io/elasticsearch-cloud-kubernetes/releases

We should add this to elastic 6.1 docker.

Fabric8 elasticsearch-cloud-kubernetes plugin 5.6.9 is now available (http://search.maven.org/remotecontent?filepath=io/fabric8/elasticsearch-cloud-kubernetes/5.6.9/elasticsearch-cloud-kubernetes-5.6.9.jar). Consider releasing Elastic 5.6.x images as long as Elastic continues to support 5.6.x branch.