[BUG] Attempting to create privileged containers produces an opaque error

[Reid D McKenzie]

Describe the bug
It would appear that the privileged: true flag in the docker-compose manifest format isn't supported. Rather than producing an error to this effect, the daemon seems to encounter an internal failure and produces a user-opaque error which had to be isolated by bisecting a services list.

To Reproduce
Steps to reproduce the behavior:
docker-compose format spec -

service:
  db2:
    image: ibmcom/db2:11.5.4.0
    container_name: divebell_db2_1
    restart: always
    privileged: true
    environment: {}
    volumes: []
    ports:
      - 50000:50000

$ exo apply docker-compose.yml
Error: posting: Post "http://localhost:43643/_exo/workspace/apply?id=e9tens6phhessw300s45pvy9fr": EOF
posting: Post "http://localhost:43643/_exo/workspace/apply?id=e9tens6phhessw300s45pvy9fr": EOF

Expected behavior
An error stating that privileged containers are not supported, or that they're a bad idea and don't do that.

System Info (please complete the following information):

• OS: Ubuntu
• Component: CLI/daemon
• Version: 2021.11.16

[Ben Elgar]

Hi @arrdem! Thank you for reporting that. I believe I've successfully reproduced and pushed a fix here: #540