portainer: Compose stack does not work - caused by mem_swappiness

Found on combination of Windows 10 + 18.03.1-ce + Portainer 1.18.1 (using local TCP 2375 connection).

When Docker is running on non-Swarm mode and hosting Windows containers if I try deploy stack like this:

version: "2"

services:
  win:
    image: microsoft/nanoserver:1803
    command: ping -t 127.0.0.1
networks:
  default:
    external:
      name: nat

it genarates error like this:

2018/07/13 10:44:55 http error: Error response from daemon: invalid option: Windows does not support MemorySwappiness (err=Error response from daemon: invalid option: Windows does not support MemorySwappiness) (code=500)

If switch to Linux containers and try deploy Linux stack like this:

version: "2"

services:
  linux:
    image: alpine:3.7
    command: sh -c "ping 127.0.0.1"
    networks:
      - web
networks:
  web:
    external:
      name: web

it works just fine.

I guess that it bug on libcompose or way how Portainer calls it and we need add exception like here is to that logic: https://github.com/hashicorp/nomad/pull/2342/files

I can investigate it more later today.

About this issue

  • Original URL
  • State: closed
  • Created 6 years ago
  • Reactions: 4
  • Comments: 17 (3 by maintainers)

Commits related to this issue

Most upvoted comments

any ETA on this bug please? i’m unable to make docker compose work on Windows …

A workaround is also welcome if any 😃