resource not working when running on coreos about docker-image-resource

[concourse-bot]

Hi there!

We use Pivotal Tracker to provide visibility into what our team is working on. A story for this issue has been automatically created.

The current status is as follows:

• #114677611 resource not working when running on coreos

This comment, as well as the labels on the issue, will be automatically updated as the status in Tracker changes.

[vito]

This will be fixed in the next release; we've confirmed this is working with the beta binaries available here:

https://github.com/vito/bin/releases

[vito]

I don't seem to have access to https://github.com/databus23/concourse-coreos - is that the right URL?

[vito]

Ah found it: https://github.com/databus23/coreos-concourse

[databus23]

@vito Ah, sorry my bad. I updated the instructions. Let me know if I can be of any further assistance in debugging this.

[vito]

Been looking into this all day, so far I'm stumped. strace just shows mount() returning ENXIO, which ain't very helpful; would need to dig into the kernel to see where that's actually coming from, which isn't fun. I was able to run the same mount command just fine on the host, but the moment I enter the container's mount namespace, it returns the error instead.

[databus23]

Yeah, same here. Bummer. At leasts its 100% reproducible. Any ideas on how to proceed? I'm not that familiar with garden linux and cloudfoundry-attic/garden-linux#45 is crushing my hopes to get support from the garden linux project. Is the linux-backend really only supported on Ubuntu? D you think its worth digging deeper or are there viable alternatives to the linux backend on the horizon that will work on more platforms ? From what I read the plan is to replace the current linux backend by a runC implementation.

I'm not really happy with running it on ubuntu as we are all in on kubernetes/CoreOS and I don't want to manage ubuntu vms anymore.

[vito]

The main focus these days is on Guardian - the aforementioned runC-based Garden backend. I have high hopes for improved portability and once it replaces Garden-Linux hopefully a bigger focus on usability.

Ubuntu is the primary target and the platform that the (pretty small) team is currently focused on supporting for production use cases, mainly to limit the scope of things the team has to worry about. I think it was tested on CentOS at one point; most things should just work, but containerization is a nightmarish hellscape to tackle when it comes to portability (kernel versions alone change everything).

/cc @julz @goonzoid (Garden PMs/contributors who I don't want to speak too much for)

[databus23]

For what its worth, I got a PR in garden-linux handling grouped cgroup mounts (cloudfoundry-attic/garden-linux#62). Still no luck with running a worker on cores though. The mount namespace inside the garden container is still acting up.

[pauldub]

Hi, I would like to report the same issue happening on an Ubuntu 14.04 server (from scaleway.com).

Some basic informations about the box:

paul@concourse-worker-1:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 14.04.4 LTS
Release:        14.04
Codename:       trusty
paul@concourse-worker-1:~$ uname -a
Linux concourse-worker-1 4.4.4-std-3 #1 SMP Tue Mar 8 17:31:34 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

What informations would you need to debug this issue? Can I help?

[concourse-bot]

Hello again!

All stories related to this issue have been accepted, so I'm going to automatically close this issue.

At the time of writing, the following stories have been accepted:

• #114677611 resource not working when running on coreos

If you feel there is still more to be done, or if you have any questions, leave a comment and we'll reopen if necessary!