Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Invalid type in volume, it should be a string. #4763

Closed
NicolasRannou opened this issue Apr 26, 2017 · 3 comments
Closed

Invalid type in volume, it should be a string. #4763

NicolasRannou opened this issue Apr 26, 2017 · 3 comments
Labels
kind/question

Comments

@NicolasRannou
Copy link

Trying to setup a bind volume and it does not work:

Followed the documentation to write the docker-compose file:

version: '3'
services:
  web:
    #build: .
    image: fnndsc/fnndsc.babymri.org
    ports:
      - "8060:8080"
    volumes:
      - type: bind
        source: .
        target: /src/website
    labels:
      name: "FNNDSC Web App"
      role: "FNNDSC Web App development server"

Docker version 17.03.1-ce, build c6d412e

docker-compose version 1.12.0, build b31ff33

docker-compose up:

ERROR: The Compose file './docker-compose.yml' is invalid because:
services.web.volumes contains an invalid type, it should be a string
@shin-
Copy link

shin- commented Apr 26, 2017

You need version: '3.2' for the extended notation.

@NicolasRannou
Copy link
Author

Thanks!

@rcdailey
Copy link

This is helpful. I assumed that '3' implied the latest version of the 2nd component, but apparently you have to explicitly specify and subsequently upgrade the 2nd component of the version.

lardbit pushed a commit to lardbit/nefarious that referenced this issue Jun 21, 2019
use bind mounts which solves a Windows specific issue regarding file …
c71fe1e 
…vs directory mounting

docker/compose#4763
@devpolo devpolo mentioned this issue Apr 12, 2021
Merged
5 tasks
prittt added a commit to oncodash/oncodash that referenced this issue Nov 25, 2021
@prittt
fix: file content require a higher version
539c33f 
More details available at docker/compose#4763.
ericonr added a commit to lnls-dig/rffe-epics-ioc that referenced this issue Jun 13, 2023
@ericonr
docker: add autosave dir bind mount.
eba3c0d 
We need a higher version, per [1].

[1] docker/compose#4763
ericonr pushed a commit to lnls-dig/rffe-epics-ioc that referenced this issue Jun 14, 2023
@henriquesimoes @ericonr
deploy: Add docker-compose to launch IOCs
7b11b7d 
This configuration follows the current deploy setting at Sirius. Some
key points here are:

Compose file version 3.2 is used to allow us to bind mount the autosave
directory [1]. It works with the version of docker-compose we have.

Several different services are used to make it possible to have a
different container for each BPM slot (and RFFE). Thus, a base
configuration has been set and is inherited for each service. However,
using the base service for the environment and then appending to it
inside a service doesn't work in the version of docker-compose we have
on our crates, so we need to declare the full environment in each one.

In our current configuration, all crates use the same local network
addresses for RFFEs. This means we can include this configuration
directly in this configuration file.

Co-authored-by: Érico Nogueira <erico.rolim@lnls.br>

[1] docker/compose#4763
ericonr pushed a commit to lnls-dig/rffe-epics-ioc that referenced this issue Jun 14, 2023
@henriquesimoes @ericonr
deploy: Add docker-compose to launch IOCs
ad5b53f 
This configuration follows the current deploy setting at Sirius. Some
key points here are:

Compose file version 3.2 is used to allow us to bind mount the autosave
directory [1]. It works with the version of docker-compose we have.

Several different services are used to make it possible to have a
different container for each BPM slot (and RFFE). Thus, a base
configuration has been set and is inherited for each service. However,
using the base service for the environment and then appending to it
inside a service doesn't work in the version of docker-compose we have
on our crates, so we need to declare the full environment in each one.

In our current configuration, all crates use the same local network
addresses for RFFEs. This means we can include this configuration
directly in this configuration file.

Co-authored-by: Érico Nogueira <erico.rolim@lnls.br>

[1] docker/compose#4763
henriquesimoes added a commit to lnls-dig/rffe-epics-ioc that referenced this issue Jun 14, 2023
@henriquesimoes
deploy: Add docker-compose to launch IOCs
b4a276e 
This configuration follows the current deploy setting at Sirius. Some
key points here are:

Compose file version 3.2 is used to allow us to bind mount the autosave
directory [1]. It works with the version of docker-compose we have.

Several different services are used to make it possible to have a
different container for each BPM slot (and RFFE). Thus, a base
configuration has been set and is inherited for each service. However,
using the base service for the environment and then appending to it
inside a service doesn't work in the version of docker-compose we have
on our crates, so we need to declare the full environment in each one.

In our current configuration, all crates use the same local network
addresses for RFFEs. This means we can include this configuration
directly in this configuration file.

Co-authored-by: Érico Nogueira <erico.rolim@lnls.br>

[1] docker/compose#4763
henriquesimoes added a commit to lnls-dig/rffe-epics-ioc that referenced this issue Jun 16, 2023
@henriquesimoes
deploy: Add docker-compose to launch IOCs
655c72f 
This configuration follows the current deploy setting at Sirius. Some
key points here are:

Compose file version 3.2 is used to allow us to bind mount the autosave
directory [1]. It works with the version of docker-compose we have.

Several different services are used to make it possible to have a
different container for each BPM slot (and RFFE). Thus, a base
configuration has been set and is inherited for each service. However,
using the base service for the environment and then appending to it
inside a service doesn't work in the version of docker-compose we have
on our crates, so we need to declare the full environment in each one.

In our current configuration, all crates use the same local network
addresses for RFFEs. This means we can include this configuration
directly in this configuration file.

Co-authored-by: Érico Nogueira <erico.rolim@lnls.br>

[1] docker/compose#4763
@saratvemulapalli saratvemulapalli mentioned this issue Jan 24, 2024
Merged
6 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/question
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@NicolasRannou @shin- @rcdailey