#I've Broken It - Failed to Create Base Fs Error

1 messages · Page 1 of 1 (latest)

hollow prawn
#

Hi, I was playing at pulling the Dagger engine Docker image through my Artifactory instance. During this I seemed to have broken my setup. Even without the Artifactory setup and pulling from the Internet as standard I get an error about failing to create the base fs
✔ connect 0.2s ✘ load module 0.1s ! failed to get configured module: input: moduleSource failed to load local module source context: select: failed to get content hash: failed to get snapshot: failed to sync: failed to create local fs: failed to create base fs: resolve : lstat /var/lib/dagger/worker/snapshots/snapshots/4/fs/mnt: no such file or directory │ ✘ finding module configuration 0.1s │ ! input: moduleSource failed to load local module source context: select: failed to get content hash: failed to get snapshot: failed to sync: failed to create local fs: failed to create base fs: resolve : lstat /var/lib/dagger/worker/snapshots/snapshots/4/fs/mnt: no such file or directory │ │ ✘ moduleSource(refString: "."): ModuleSource! 0.0s │ │ ! failed to load local module source context: select: failed to get content hash: failed to get snapshot: failed to sync: failed to create local fs: failed to create base fs: resolve : lstat /var/lib/dagger/worker/snapshots/snapshots/4/fs/mnt: no such file or directory

Can someone help me fix this as I'm not clear on what's happened.

strong grail
#

that should fix it

hollow prawn
#

Yeah I've removed the container, image and volumes and used docker system prune -a and docker volume prune -a and still have the same.
For info I'm running it in Ubuntu on WSL on Windows

hollow prawn
#

Other Docker containers seem to be OK. Prometheus and Grafana I have running it are OK and the Docker hello-world worked OK too

strong grail
#

@hollow prawn that's very strange indeed. Have 5 mins to jump into a quick #911305510882513037 session?

#

to check it out together?

hollow prawn
#

Sure. From some work I've just done it doesn't appear to be mounting the current working directory into the container volume

strong grail
hollow prawn
#

Right, a subtle one this.
I had managed to drop the case on one of my subfolders
I am working in a folder in Windows called
C:\Code\dagger-simple-poc-use
In WSL I was in the folder (note the lower case c on code - WSL seems to allow me to ignore the case)
/mnt/c/code/dagger-simple-poc-use

So when trying to run the dagger functions in there Dagger/Docker couldn't mount it as the current directory path had the wrong case
Changing to work in
/mnt/c/Code/dagger-simple-poc-use
got it working again.

hazy falcon
strong grail