ypereirareis / docker-satis Goto Github PK

It's possible to pull a private key from an environment variable and set it when the container runs. An example of this is at https://github.com/realpage/asset-publisher/blob/master/infrastructure/start.sh#L14. The Dockerfile's CMD is then set to run the script before hitting the process that Docker keeps running. Implementing this step would be a great step towards this container not having to be rebuilt with custom config.

Hi There,

Looking at getting this setup for our dev environment, but can't see how to persist the satis builds so that they survive docker restarts?

Cheers

CRONTAB_FREQUENCY won't effect on /etc/cron.d/satis-cron because you are overwriting it on line 68 of /app/scripts/startup.sh just after injecting CRONTAB_FREQUENCY on line 57

Adding a repo to satis through the admin interface returns two exceptions :
IOException in FilePersister.php line 117: Path "/app/config.json" is not writeable.
and
RuntimeException in FilePersister.php line 82: Unable to persist the data to "/app/config.json"
The file is set through a volume with : ./data/config/config.json:/app/config.json:rwand if I edit it on the host or in the docker container, in can see the changes both way.
Why isn't it writeable through satisfy ? rights conflicts between www-data and root ?

Hi,

The install runs the build before the crontab is updated. If the build takes a long time then the default cron will rerun the build many times in parallel. I moved the setting of the cron prior to the first build to address this. Thanks for your work.

• RUN apt-get clean && rm -rf /var/lib/apt/lists/* /tmp/* /var/tmp/*
  • apt-get install --no-install-recommends
  • Composer update outsite of the image => startup.sh script

Hello there,

I'm struggling with this repository. Satisfy is returning ok but satis itself is returning 403 when I edit the config.json. I'm using a custom docker image based on 4.1. Could I get any hint? here a log: https://gist.github.com/jmverges/77a87b6a1384156a99e1ee61c870a6da

Regards,
Juan Manuel.

Docker compose file as follows:

satis:
    image: ypereirareis/docker-satis:4.2
    ports:
        - 8888:3000
        - 5000:80

@ port 5000, satis looks good.
@ port 8888 I get Cannot GET /

Same for requesting /admin - Cannot GET /admin

Launching the startup script manually returns an error :
Permissions 0754 for '/root/.ssh/id_rsa' are too open.
The file is set with a chmod 600 on the host.

The current image uses Ubuntu 15.10 as a base, which has been EOL since July 28, 2016.

Updating this to 16.04 or 18.04 does require either adding ppa:ondrej/php repo to apt (This drops support for php-apc though since this does not seem available anymore for PHP 5.6), or switching to php7.

I didn't test what switching PHP versions would do, but either solution makes sure that at least the OS is still supported for a while to come.

E: There are problems and -y was used without --force-yes
Service 'satis' failed to build: The command [/bin/sh -c apt-get install -y nginx] returned a non-zero code: 100

Hello and first thanks for share that work.
Here my case, i installed gitlab with docker from the repository sameersbn/docker-gitlab, it's work well. I added satis container parameters on the given compose file. But i can't understand how does ssh work in your scenario, in the doc it's say that "The container needs to know the ssh key you added in your private repo." so we speak about a Public key, so id_rsa.pub is'nt it ?
Other thing, i don't know if with docker 1.9.1 with consideration of the gitlab compose file and the use of "links" parameter i need to add another one in satis section even if i put in PRIVATE_REPO_DOMAIN_LIST env the IP address of my gitlab container.

Satis is working with 1.2.2 composer version, but gitlab-token appear in 1.3, your startup script must update composer composer update composer/composer before starting server as so the user may enter Gitlab-token section in config.json to work with Gitlab.

The composer offers an authentication for each repository (see here).

It would be nice if the nginx proxy inside the container would offer the last two methods.

Does it needs to use -v $(pwd):/app as a workdir with this repository sources cloned?

Using the latest version of the docker image, satis returns a 403 error. It seems like Supervisor is not launched at startup.
I would gladly provide more infos if you could tell me where to find them.