Code Monkey home page Code Monkey logo

Comments (5)

jgedarovich avatar jgedarovich commented on September 28, 2024 2

bump - also ran into this bug

from cloud-builders-community.

mhrst avatar mhrst commented on September 28, 2024

I've also been running into this issue lately and couldn't track down the cause. It works fine running in the Cloud, but local doesn't seem to mount volumes correctly. Usually it's empty, but one of my services has a few of the sub-folders visible. However, those sub-folders are also empty. I've tried relative and absolute paths.

I've also tried defining volumes separately (after the steps: section). Doing it this way creates a file-not-found error at least:

volumes:
  data:
    driver_opts:
      type: none
      device: /path-to-data
      o: bind

from cloud-builders-community.

amalhotragannett avatar amalhotragannett commented on September 28, 2024

Is there a work-around for this issue?

from cloud-builders-community.

JackCA avatar JackCA commented on September 28, 2024

@Philmod sorry to ping, but wondering if you have thoughts on this?

Maybe you have an idea of root cause?

from cloud-builders-community.

samhiatt avatar samhiatt commented on September 28, 2024

I've ran into this issue as well, except with images based on 'gcr.io/cloud-builders/docker'. I was able to get mounted volumes to show up in 'gcr.io/cloud-builders/gsutil' layers, but only if I first include a step that calls docker run, explicitly mounting the volumes like this:

  - name: 'gcr.io/cloud-builders/docker'
    args: [ "run", "--rm", "-v", "vol1:/output", "gcr.io/$PROJECT_ID/tdc:latest"]
    volumes:
      - name: 'vol1'
        path: '/output'

Then the following step will correctly list the expected contents of /output:

  - name: 'gcr.io/cloud-builders/gsutil'
    entrypoint: "bash"
    args: [ "-c", "ls", "-l", "/workspace" ]
    volumes:
      - name: 'vol1'
        path: '/output'

However, the mounted volume /workspace is empty in the image 'cloud-builders-community/firebase', for example if I include a step like this:

  - name: 'gcr.io/$PROJECT_ID/firebase'
    entrypoint: 'bash'
    args: ['-c', 'ls', '-l', '/output', '.']
    volumes:
      - name: 'vol1'
        path: '/output'

I'm not sure if there's something I'm doing wrong or if it's a bug. Any help would be appreciated.

from cloud-builders-community.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.