Rebuild & push images

[rcdailey]

An issue related to running as an arbitrary user was fixed recently in the php:7.2-apache-stretch image (See docker-library/php#755 and docker-library/php#745).

I verified the following configuration works:

version: '3.7'

services:
  app:
    image: php:7.2-apache-stretch
    user: $UID:$GID
    network_mode: bridge
    sysctls:
      - net.ipv4.ip_unprivileged_port_start=0
    ports:
      - 50080:80
    volumes:
      - ./app:/var/www/html
      - ./data:/data
      - /etc/localtime:/etc/localtime:ro
    environment:
      - APACHE_RUN_USER=#$UID
      - APACHE_RUN_GROUP=#$GID

However, nextcloud:apache will not benefit from these changes unless you rebuild & publish again, I believe. Have you automated your deployment process so this will get handled eventually? Or must this be manually done?

[tilosp]

It's fully automated, after the php image is build it will trigger a rebuild of all child images including nextcloud.

[rcdailey]

Well then the issue isn't fixed yet in Nextcloud image. I tested last night on Nextcloud:Apache and I got var log permission errors. How can I verify the latest upstream images are included in your build?

…

On Thu, Nov 29, 2018, 3:20 AM Tilo Spannagel ***@***.***> wrote: Closed #558 <#558>. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#558 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABr6dj65EnnfD8rktuVLrxKw0wPbGbx3ks5uz6bDgaJpZM4Y4wFw> .

[rcdailey]

@tilosp Could I please get your help identifying why the images do not seem to be updated? If it's automated, is this a timing issue? Should I check in a day? Can we reopen this issue until I'm able to verify the upstream changes are included?

[rcdailey]

Sorry, replied too soon: Pulled again, tested, and everything is working great 👍