profile
viewpoint

startedalpine-docker/socat

started time in 7 days

startedNitro/envoy-ui

started time in 10 days

issue commentdocker/app

Subkeys render error - max_replicas_per_node

@silvin-lubecki Thanks for the suggestion. I hope to send the PR in the next couple of days.

johnbizokk

comment created time in a month

issue openedmoby/moby

Non-working Buildkit GC policies

<!-- If you are reporting a new issue, make sure that we do not have any duplicates already open. You can ensure this by searching the issue list for this repository. If there is a duplicate, please close your issue and add a comment to the existing issue instead.

If you suspect your issue is a bug, please edit your issue description to include the BUG REPORT INFORMATION shown below. If you fail to provide this information within 7 days, we cannot debug your issue and will close it. We will, however, reopen it if you later provide the information.

For more information about reporting issues, see https://github.com/moby/moby/blob/master/CONTRIBUTING.md#reporting-other-issues


GENERAL SUPPORT INFORMATION

The GitHub issue tracker is for bug reports and feature requests. General support for docker can be found at the following locations:

  • Docker Support Forums - https://forums.docker.com
  • Slack - community.docker.com #general channel
  • Post a question on StackOverflow, using the Docker tag

General support for moby can be found at the following locations:

  • Moby Project Forums - https://forums.mobyproject.org
  • Slack - community.docker.com #moby-project channel
  • Post a question on StackOverflow, using the Moby tag

BUG REPORT INFORMATION

Use the commands below to provide key information from your environment: You do NOT have to include this information if this is a FEATURE REQUEST -->

Description

Suddenly, we cannot use the builder garbage collector policy as described in the PR https://github.com/moby/moby/pull/37846 and explained by the Docker Captain (@sudo-bmitch) report in the latest DockerCon - Tips and Tricks of the Docker Captains. Also, I am frustrating why so many cool features do not have related documentation. On the evaluation cycle, the build cache garbage collector disregards the defined policies and drops the cache to the lowest value of the keepStorage key in the set of the rules.

Steps to reproduce the issue:

  1. Run the docker system df command to check the currect disk usage of the build cache stored localy
  2. Create the docker daemon config file with the following content - see the Annex №1 below
  3. Run the build of the whatever docker image you have to produce the build cache and evaluate the garbage collection (greater than the smallest size defined in the policies)
  4. Run the docker system df command to check the currect disk usage of the build cache stored localy
  5. Reload the docker daemon
  6. Run the build of the whatever docker image you have to produce the build cache and evaluate the garbage collection (at least - 300mb) - Optional
  7. Run the docker system df command to check the currect disk usage of the build cache stored localy

Describe the results you received:

At the end of manipulations, which described above - I lost my build cache and the size of the remained cache equal to the smallest keepStorage policy I have defined in the docker daemon config.

Describe the results you expected:

I am expecting the garbage collector to respect and follow the policy defined in the docker daemon config.

Additional information you deem important (e.g. issue happens only occasionally):

According to the current garbage collector behavior, we forced to use only one policy that limits the maximum size of the build cache, which remains on the disk.

Output of docker version:


Client: Docker Engine - Community
 Version:           19.03.3
 API version:       1.40
 Go version:        go1.12.10
 Git commit:        a872fc2f86
 Built:             Tue Oct  8 00:58:10 2019
 OS/Arch:           linux/amd64
 Experimental:      true

Server: Docker Engine - Community
 Engine:
  Version:          19.03.3
  API version:      1.40 (minimum version 1.12)
  Go version:       go1.12.10
  Git commit:       a872fc2f86
  Built:            Tue Oct  8 00:56:46 2019
  OS/Arch:          linux/amd64
  Experimental:     true
 containerd:
  Version:          1.2.10
  GitCommit:        b34a5c8af56e510852c35414db4c1f4fa6172339
 runc:
  Version:          1.0.0-rc8+dev
  GitCommit:        3e425f80a8c931f88e6d94a8c831b9d5aa481657
 docker-init:
  Version:          0.18.0
  GitCommit:        fec3683

Output of docker info:


Client:
 Debug Mode: false
 Plugins:
  app: Docker Application (Docker Inc., v0.8.0)
  buildx: Build with BuildKit (Docker Inc., v0.3.1-tp-docker)

Server:
 Containers: XX
  Running: XX
  Paused: XX
  Stopped: XX
 Images: XX
 Server Version: 19.03.3
 Storage Driver: overlay2
  Backing Filesystem: xfs
  Supports d_type: true
  Native Overlay Diff: true
 Logging Driver: local
 Cgroup Driver: cgroupfs
 Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
 Swarm: active
  NodeID: ID
  Is Manager: true
  ClusterID: ID
  Managers: X
  Nodes: X
  Default Address Pool: XX.XX.XX.XX/X
  SubnetSize: 24
  Data Path Port: XXXX
  Orchestration:
   Task History Retention Limit: 5
  Raft:
   Snapshot Interval: 10000
   Number of Old Snapshots to Retain: 0
   Heartbeat Tick: 1
   Election Tick: 10
  Dispatcher:
   Heartbeat Period: 5 seconds
  CA Configuration:
   Expiry Duration: 3 months
   Force Rotate: 0
  Autolock Managers: false
  Root Rotation In Progress: false
  Node Address: XX.XX.XX.XX
  Manager Addresses:
   XX.XX.XX.XX:XXXX
 Runtimes: runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: b34a5c8af56e510852c35414db4c1f4fa6172339
 runc version: 3e425f80a8c931f88e6d94a8c831b9d5aa481657
 init version: fec3683
 Security Options:
  seccomp
   Profile: default
 Kernel Version: 5.3.6-1.el7.elrepo.x86_64
 Operating System: CentOS Linux 7 (Core)
 OSType: linux
 Architecture: x86_64
 CPUs: XX
 Total Memory: XX.XGiB
 Name: NAME
 ID: ID
 Docker Root Dir: /var/lib/docker
 Debug Mode: false
 Registry: https://index.docker.io/v1/
 Labels:
  processor-cores=XX
 Experimental: true
 Insecure Registries:
  127.0.0.0/8
 Live Restore Enabled: false

WARNING: bridge-nf-call-ip6tables is disabled

Additional environment details (AWS, VirtualBox, physical, etc.):

Annex №1 (daemon.json)


{
  "experimental": true,
  "features": {
    "buildkit": true
  },
  "builder": {
    "gc": {
      "enabled": true,
      "defaultKeepStorage": "200GB",
      "policy": [
        {"keepStorage": "256MB", "filter": {"unused-for": {"960h": true}}},
        {"keepStorage": "1GB", "filter": {"unused-for": {"480h": true}}},
        {"keepStorage": "2GB", "filter": {"unused-for": {"360h": true}}},
        {"keepStorage": "5GB", "filter": {"unused-for": {"240h": true}}},
        {"keepStorage": "10GB", "filter": {"unused-for": {"192h": true}}},
        {"keepStorage": "20GB", "filter": {"unused-for": {"144h": true}}},
        {"keepStorage": "40GB", "filter": {"unused-for": {"120h": true}}},
        {"keepStorage": "60GB", "filter": {"unused-for": {"96h": true}}},
        {"keepStorage": "80GB", "filter": {"unused-for": {"48h": true}}},
        {"keepStorage": "100GB", "filter": {"unused-for": {"1m": true}}},
        {"keepStorage": "200GB", "all":  true}
      ]
    }
  }
}

created time in a month

issue commentdocker/app

Subkeys render error - parallelism and max_failure_ratio

@silvin-lubecki Hello! Is there any visible date of the next release of the Docker App, which will include the latest fixes (for example - this one)? Is there any release cycle of the Docker App or some interconnection between the Docker App and some significant updates of the Docker CE? From my point of view, the release cycle of the subordinate projects strongly connected to the final release stage of the new Docker CE version.

johnbizokk

comment created time in a month

issue openeddocker/app

Subkeys render error - max_replicas_per_node

<!-- If you are reporting a new issue, make sure that we do not have any duplicates already open. You can ensure this by searching the issue list for this repository. If there is a duplicate, please close your issue and add a comment to the existing issue instead.

If you suspect your issue is a bug, please edit your issue description to include the BUG REPORT INFORMATION shown below. If you fail to provide this information within 7 days, we cannot debug your issue and will close it. We will, however, reopen it if you later provide the information.

For more information about reporting issues, see https://github.com/docker/app/blob/master/CONTRIBUTING.md#reporting-other-issues


GENERAL SUPPORT INFORMATION

The GitHub issue tracker is for bug reports and feature requests. General support can be found at the following locations:

  • Docker Support Forums - https://forums.docker.com
  • Docker Community Slack - https://dockr.ly/community
  • Post a question on StackOverflow, using the Docker tag

BUG REPORT INFORMATION

Use the commands below to provide key information from your environment: You do NOT have to include this information if this is a FEATURE REQUEST -->

Description

The latest version of the Docker CE distribution introduced the schema version (3.8) which supports the new key in the deploy section of the service declaration - max_replicas_per_node. In the meantime, this key doesn't have a related interpolation type in the - interpolate.go. Also, it looks similar to the following issue - https://github.com/docker/app/issues/559.

Steps to reproduce the issue:

  1. Create the docker-compose file with the following content - see the Annex №1 below
  2. Create the parameters.yml file with the following content - see the Annex №2 below
  3. Create the metadata.yml file with the following content - see the Annex №3 below
  4. Execute the following command - docker app render

Describe the results you received:

Unfortunately, we have received the following errors:

  • render failed: Action "com.docker.app.render" failed: failed to load Compose file: services.php-fpm.deploy.placement.max_replicas_per_node must be a integer

Describe the results you expected:

We are expecting from the docker app binary to render the values correctly.

Additional information you deem important (e.g. issue happens only occasionally):

Output of docker version:

Client: Docker Engine - Community
 Version:           19.03.3
 API version:       1.40
 Go version:        go1.12.10
 Git commit:        a872fc2f86
 Built:             Tue Oct  8 00:58:10 2019
 OS/Arch:           linux/amd64
 Experimental:      true

Server: Docker Engine - Community
 Engine:
  Version:          19.03.3
  API version:      1.40 (minimum version 1.12)
  Go version:       go1.12.10
  Git commit:       a872fc2f86
  Built:            Tue Oct  8 00:56:46 2019
  OS/Arch:          linux/amd64
  Experimental:     true
 containerd:
  Version:          1.2.10
  GitCommit:        b34a5c8af56e510852c35414db4c1f4fa6172339
 runc:
  Version:          1.0.0-rc8+dev
  GitCommit:        3e425f80a8c931f88e6d94a8c831b9d5aa481657
 docker-init:
  Version:          0.18.0
  GitCommit:        fec3683

Output of docker app version:


Version:               v0.8.0
Git commit:            7eea32b
Built:                 Tue Oct  8 01:00:29 2019
OS/Arch:               linux/amd64
Experimental:          off
Renderers:             none
Invocation Base Image: docker/cnab-app-base:v0.8.0

Output of docker info:


Client:
 Debug Mode: false
 Plugins:
  app: Docker Application (Docker Inc., v0.8.0)
  buildx: Build with BuildKit (Docker Inc., v0.3.1-tp-docker)

Server:
 Containers: XX
  Running: XX
  Paused: XX
  Stopped: XX
 Images: XX
 Server Version: 19.03.3
 Storage Driver: overlay2
  Backing Filesystem: xfs
  Supports d_type: true
  Native Overlay Diff: true
 Logging Driver: local
 Cgroup Driver: cgroupfs
 Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
 Swarm: active
  NodeID: ID
  Is Manager: true
  ClusterID: ID
  Managers: X
  Nodes: X
  Default Address Pool: XX.XX.XX.XX/X
  SubnetSize: 24
  Data Path Port: XXXX
  Orchestration:
   Task History Retention Limit: 5
  Raft:
   Snapshot Interval: 10000
   Number of Old Snapshots to Retain: 0
   Heartbeat Tick: 1
   Election Tick: 10
  Dispatcher:
   Heartbeat Period: 5 seconds
  CA Configuration:
   Expiry Duration: 3 months
   Force Rotate: 0
  Autolock Managers: false
  Root Rotation In Progress: false
  Node Address: XX.XX.XX.XX
  Manager Addresses:
   XX.XX.XX.XX:XXXX
 Runtimes: runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: b34a5c8af56e510852c35414db4c1f4fa6172339
 runc version: 3e425f80a8c931f88e6d94a8c831b9d5aa481657
 init version: fec3683
 Security Options:
  seccomp
   Profile: default
 Kernel Version: 5.3.6-1.el7.elrepo.x86_64
 Operating System: CentOS Linux 7 (Core)
 OSType: linux
 Architecture: x86_64
 CPUs: XX
 Total Memory: XX.XGiB
 Name: NAME
 ID: ID
 Docker Root Dir: /var/lib/docker
 Debug Mode: false
 Registry: https://index.docker.io/v1/
 Labels:
  processor-cores=XX
 Experimental: true
 Insecure Registries:
  127.0.0.0/8
 Live Restore Enabled: false

WARNING: bridge-nf-call-ip6tables is disabled

Additional environment details (AWS, VirtualBox, physical, etc.):

Annex №1 (docker-compose.yml)


version: '3.8'
x-preferences: &default-preferences
  preferences:
    - spread: "${placement.preferences.labels}"
x-constraints: &default-constraints
  constraints:
    - "node.hostname == ${placement.constraints.node.hostname}"
x-placement: &default-placement
  placement:
    max_replicas_per_node: ${placement.max_replicas}
    <<: [ *default-preferences, *default-constraints ]
services:
  php-fpm:
    image: 'php'
    deploy:
      *default-placement

Annex №2 (parameters.yml)


placement:
  preferences:
    labels: node.labels.guest-master
  constraints:
    node:
      hostname: docker.app.test
  max_replicas: 1

Annex №3 (metadata.yml)


version: 1.0.0
name: yet-another-project
description: "project description"
namespace: "domain.com/yap"
maintainers:
  - name: contributor
    email: "contributor@domain.com"

created time in a month

startedweaveworks/ignite

started time in a month

startedtimberio/vector

started time in 2 months

issue commentmoby/moby

Example Buildkit GC configuration results in daemon error

The problem also persists in the 19.03.2 version. The fix proposed by issue reporter fixes the issue.

KevOrr

comment created time in 2 months

startedlesovsky/pgcenter

started time in 2 months

startedshift/domain_exporter

started time in 2 months

startedComcast/trickster

started time in 2 months

startedapache/incubator-pagespeed-ngx

started time in 2 months

startedeustas/ngx_brotli

started time in 3 months

startedlukaszlach/clip

started time in 3 months

startedbazelbuild/bazel

started time in 3 months

startedappbaseio/dejavu

started time in 3 months

startedportainer/portainer

started time in 3 months

more