itisfoundation / dockerfiles Goto Github PK

Dependabot couldn't find a Dockerfile for this project.

Dependabot requires a Dockerfile to evaluate your project's current Docker dependencies. It had expected to find one at the path: /python-with-pandas/3.6-alpine/Dockerfile.

If this isn't a Docker project, or if it is a library, you may wish to disable updates for it from within Dependabot.

View the update logs.

blackfynn library takes VERY long to install in alpine because it contains pandas therefore services like storage would benefit from a pre-built base image with blackfynn requirements pre-installed in a python2 virtualenv

See discussion about installing pandas in alpine linux

• Setup CI to build, test and release (tag+push) dockerfiles into itisfoundation @ dockerhub registry
• The CI has to be uniform to all projects in the repo
• Update README.md with useful info on the workflow
• Add .github configuration. See e.g. here

Ensure that:

• every project has a minimal common layout:
  • a Makefile with minimal common interface
  • a docker-compose.yml with build section
• pushed image tags SHALL not be re-written!! Ensure as well that new pushes correspond to newer versions?
• use commit id as tag
• make sure can only release from master branch of main repository (ITISFoundation).
  • Ensure all projects have
  • At this point, freeze the version QOOXDOO_KIT_TAG in services/web/client/Makefile

Some good references

• https://github.com/dockerfile/ubuntu: http://dockerfile.github.io/

A collection of node-based tools that shall be used to replace node in any system.

Containerized tools reduces system requirements, gain control on the version and preserves compatibility in the target system.

Typically, developing/deploying requires some tooling that is expected installed in the host. This tooling shall be provided with this type of toolboxes or essentials collection

Containers like python-toolbox, a node-toolbox is for ITIS group what the busybox is to embedded linux systems ... an essential collection

Some use cases:

• npm install -g npm-check-updates (see https://flaviocopes.com/update-npm-dependencies/) is needed in makefile of qooxdoo-kit. Having

There is currently no check that service keys for different services are unique. If a new service is created with the same key as an existing one, that new service will overwrite the previous one in the service catalog. This should probably be checked in:

https://git.speag.com/oSparc/sparc-external
https://git.speag.com/oSparc/sparc-internal
https://github.com/ITISFoundation/osparc-services

key=name of the service.
One solution : check in the CI if a service already exists before adding a new one ?

Some commands in the README seems outdated.

Could you also make the project compatible with the Travis pipeline ?

Here are the steps to follow :

I recommend you to takes the files from the folder DEVPI which are following all the requirements.

1. Create a folder and give to this folder the name of your project. At the root of this folder have to be present :
   1. A docker-compose.yml file (MANDATORY)
   2. A Makefile with the usual commands (build, build-nc, test, up, down, tag, release, info, clean). (MANDATORY)
   3. A VERSION file. This file is also MANDATORY as it is used for the tag system that will tag the docker'images before sending them to Docker'hub. The versioning MUST follow this format : X.X.X , example : 1.5.6
   4. A test folder (RECOMMANDED)
   5. A Dockerfile (Mandatory)

follow checklist and script for next time

• badges (main + per dockerfile)
• PR review
• .github templates
• setup travis:
• deploy:
  • dockerhub doc?
  • dockerhub hooks -> microbadger
• define auto test/usage with metadata?

Dependabot couldn't find a Pipfile for this project.

Dependabot requires a Pipfile to evaluate your project's current Python dependencies. It had expected to find one at the path: /python-with-pandas/3.6-alpine/Pipfile.

If this isn't a Python project, or if it is a library, you may wish to disable updates for it from within Dependabot.

View the update logs.

• makefile with review tag, release cycle
• add CI in travis to test and deploy

Image with json-schema-faker

• Dockerfile with a service to create fake data from schema
• expose json-schema-faker API via a webserver
• add image as a service in docker-compose
• tests query web API passing jsonschema and returns fake data
• add this in ITISFoundation/dockerfile

:~/devp/itis-dockerfiles/qooxdoo-kit$ make info
[WARN tini (6)] Tini is not running as PID 1 and isn't registered as a child subreaper.
Zombie processes will not be re-parented to Tini, so zombie reaping won't work.
To fix the problem, use the -s option or set the environment variable TINI_SUBREAPER to register Tini as a child subreaper, or run Tini as PID 1.
[RUN]: Running command (cat package.json) as node(1000):node(1000)
cat: can't open 'package.json': No such file or directory
Makefile:74: recipe for target 'info' failed