fs-utils | Generalized file and path utils for Node.js projects | File Utils library

That's now how you insert a variable into a string :-)

If you have a reasonably modern Python version you can use f-strings like this:

use ls -ld /usr/share to see what the permissions on the directory are (without -d, you get the contents and their permissions).

Use code like:

Allowing a container to perform a filesystem mount would be a security vulnerability, allowing a container escape to the host.

You cannot do this at build time in the Dockerfile. Instead you should configure the container with a volume mount. Support for this was added earlier this year.

This error happens because you're trying to mount a device inside the build step. At this point, these capabilities aren't available for the build container to use and it seems to be rolling out as a flag for disabling security at buildkit rather than enabling custom capabilities at build time.

The usual way to do that is to have your CIFS mount ready when you start your build process, as it'd not expose any authentication, device or mount point, as well as it's easier for docker to handle changes and react to them (since the build process works hard to cache everything before building it).

If you still want to do that, you'll need a few extra steps to enable the insecure flags from both the buildkitd and the docker buildx:

Mind that, as of today (2020-09-09), the support is still experimental and unforeseen consequences can happen.

1. Ensure that you're using docker version 19.03 or later.
2. Enable the experimental features, by adding the key "experimental":"enabled" to your ~/.docker/config.json
3. Create and use a builder that has the security.insecure entitlement enabled:

I managed to sort it out myself. I used Ubuntu 18.04 AMI instead of Linux as it supports latest versions of PHP and Apache.

Also had to change the "UserData" a bit:

Stop data don't have route_id field.

You should try other data, such as Trip or Route

You can look at the first row in your data file to see which field do they have.

GTFS data structure here

You have a couple of issues with your regex; it will match (for example) python-kitchen-1.1.1-5.el7.noarch, nfs-utils-1.3.0-0.65.0.1.el7.x86_64, because it allows space and commas before the match to one of devel,git or nfs (in (.+?)). Also, it won't match git-1.8.3.1-20.el7.x86_64 because it requires a comma at the end of the match. You can fix those issues by replacing (.+?) with [^ ]* and \, with (,|$). Then you can use a solution derived from this question (although in my preferred form, checking for NOT NULL in the CONNECT BY) to get all your results:

I haven't found a better solution than to exclude nfs-utils packages from upgrade as described here. That works for me.

It's related to Kubernetes and how the given Persistent Volume is defined. You can check all the discussion and possible workarounds in the related GH Issue.