docker invalidate cache

docker invalidate cachehow to edit file in docker container

How much energy would it take to keep a floating city aloft? Using --password via the CLI is insecure. More like San Francis-go (Ep. What about existing files does a git pull affect those? See, https://docs.docker.com/engine/reference/commandline/login/#credentials-store, $ docker build --tag $TEST_IMAGE_BRANCH_TAG --cache-from $TEST_IMAGE_BRANCH_TAG --build-arg BUILDKIT_INLINE_CACHE=1 ". You can do this per service using the default_cache_branch directive: If the default_cache_branch directive is not present, we will always use master as your cache fallback branch by default. This should include any package installation, directory creation, or downloads. The various RUN commands should also be ordered according to frequency of invalidation. So if we want to autoscale our secondary nodes we need to make sure that they have the image cache before jobs start running. Have a question about this project? Which book should I choose to get into the Lisp World? https://github.com/moby/moby/issues/4351#issuecomment-76222745. For example, it would be very helpful if you could do something like this: @jcoffland I saw this is closed, is your suggestion taken ? To reduce the chances of this happening, strip down the number of files being added to the image to the bare essentials. We run various jobs on our Jenkins infrastructure but the most common job is for building and testing our monolith on every push to a PR and merge into master. This feature has been deprecated, because CodeShip no longer relies on registries to provide remote caching. E.g. The more files which get added to the Docker image during an ADD or COPY, the higher the chance that the image cached will be invalidated despite the functionality of the image remaining the same. I have 100 steps in my build script, and I want to only redo the step 80.. but I don't want to redo other steps. The text was updated successfully, but these errors were encountered: Would something like docker build --no-cache . By clicking Accept all cookies, you agree Stack Exchange can store cookies on your device and disclose information in accordance with our Cookie Policy. This would give us a copy of the Docker image from a recent version of the codebase along with the build cache we needed to speed up subsequent builds. That comment was from over a year ago :). Elijah McClain, George Floyd, Eric Garner, Breonna Taylor, Ahmaud Arbery, Michael Brown, Oscar Grant, Atatiana Jefferson, Tamir Rice, Bettie Jones, Botham Jean, BoringDAO Sundering + Snapshot integration. 469). A good tie breaker for this situation would also be that whichever image cache is larger should be placed higher in the file. That will be used as a cache for future executions of docker build. We can replicate this behaviour with a simple example: We have a project with two files a Dockerfile and a text file, And lets take a note of the mtime of our test file for later on. But the idea behind this solution is to try to provide a new value to break the cache each time the build is run, which can be implemented in lots of ways. Ok then! @Adr I agree. Just wondering; how did you get on 100 steps/layers? Running on runner-############## via ip-#################### 3cef1c0..1e69e71 ci -> origin/ci. How is Docker different from a virtual machine? Sign in rev2022.8.2.42721. That's precisely the feature I'd like to have. Generating Passive Income Is Hard, Here Is a Better Option, Migrating to Alibaba Clouds ApsaraDB for MongoDB for Mobile App, Local Development Pipeline Using Skaffold on Kubernetes, Workaround to run terraform after macOS Catalina/Monterey update, # Things like apt-get installs, these take a decent amount of time, # These live in our main codebase along side the code and basically never change, # There's a fair few of these, they take a while but rarely change, # This is where we expect the cache to be invalidated and copy'ing in the files doesn't take long, vagrant@vagrant-ubuntu-trusty-64:~$ cat Dockerfile, vagrant@vagrant-ubuntu-trusty-64:~$ stat test. is it very difficult to implement? So attempt #3 that turned out to be successful was to: Create a base image that we use in FROMat the start of the main Dockerfile which already has ran the expensive steps and have that pulled down to the nodes when they spin up. How do I get a YouTube video thumbnail from the YouTube API? In some cases, you may want to specify a branch other than master to use as your cache fallback. Here is a simple guide to optimizing your build: You should move all RUN steps which are not dependent on added files up to the top of your Dockerfile. We didnt see this issue before as we do the git checkout part of the job on our primary node into workspaces which are never deleted and so after an initial checkout these files are never touched and Docker never considers the early COPY steps to have been invalidated. I would have thought one can use something like this: docker build --commit 3e1670c59af1 to invalidate the cache from this point on and rebuild everything after this. Thanks for contributing an answer to Stack Overflow! This way they are unlikely to invalidate a more stable cached image as a side effect. Announcing the Stacks Editor Beta release! We dont have that step cached and so Docker just runs it. COPY .cachebust /tmp/cachebust Like.. Successfully merging a pull request may close this issue. So it looks like Docker will re-run the step (and all the steps below it) if the string I am passing to RUN command changes in anyway - even it's just a comment. Most DPR (Damage Per Round) Barbarian Build against Undead, Does this JavaScript example create race conditions? Dockers multi-stage build feature allows you to build Docker images with multiple build stages in the Dockerfile, ultimately saving an image from just the final stage. I bundled these two files into a git repo, pushed them up then pulled the repo down to a seperate folder. Trending sort is based off of the default sorting method by highest score but it boosts votes that have happened recently, helping to surface more up-to-date answers. How do I change the sans serif font in my document? You can read more about Docker multi-stage builds on our blog, but this has certain impacts on caching your image with CloudBees CodeShip Pro. If we add another file to the project push it up , and then pull it back down into the other git checkout , The existing test file is untouched and the new file appears with all the timestamps set to the time of the git pull. @snackycracky docker 1.9 adds "build time parameters", which can be used to achieve that; see http://docs.docker.com/engine/reference/builder/#arg, Doing something like docker build --build-arg commit=3e1670c59af1 .. would set the commit arg, which can be used to (e.g.) Building this Docker image from scratch takes around 10 minutes and we rely on the Docker image cache on these nodes to reduce our build times by placing the step which normally invalidates the cache (the copying of the updated codebase) at the end of the Dockerfile. Site design / logo 2022 Stack Exchange Inc; user contributions licensed under CC BY-SA. Its filename will be changed before the docker build is triggered by our build system. I initially raised this issue via Gitlab support, and I have been directed to create an issue here. WARNING! Any further RUN commands, which are dependent upon added files, should be run ONLY after adding those specific files required. The second change to code/ triggers a full rebuild. What are the possible attributes of aluminum-based blood? So, it's not possible to clear the 80th step cache, and keep using 81th step cache to 100th step cache. work for you? In Dockerfile, straight before the stage I want to cachebust: document docker deployment and management, http://docs.docker.com/engine/reference/builder/#arg. However, only slightly modifying a step should invalidate the cache, for example; I think that should re-build steps 81..100. Sometimes commands return exit 0 but end up in a failed state. Attempt #1 was to simply pull down a copy of the image from our registry in the Cloudformation userdata when the node comes up. In order to fully utilize the caching provided by CodeShip, you should optimize your Docker builds to take advantage of the Docker image cache. As long as long Docker caching mechanism does not change, a similar way can be found. Automate all the things! Is there anything a dual bevel mitre saw can do that a table saw can not? Why classical mechanics is not able to explain the net magnetization in ferromagnets? From inside of a Docker container, how do I connect to the localhost of the machine? privacy statement. By clicking Sign up for GitHub, you agree to our terms of service and And there we have it, we now spend less money and have more Jenkins capacity during the day when we need it! A good rule of thumb for this process is if the resulting image will not utilize a file or folder, add it to the .dockerignore file. You signed in with another tab or window. In previous versions of Jet, you were able to use the remote cache when running a local build with jet steps. Your password will be stored unencrypted in /root/.docker/config.json. This means that for now its possible that your build may take a bit longer if you relied on caching all of the layers to speed up the build. That would give the possibility to do a quick check based on the HTTP headers to decide whether a cached layer could be used or not. This gets me a feedback loop I can live with! Announcing Design Accessibility Updates on SO, Private module not updating inside docker, Docker-compose does not reflect changes in requirements.txt, How to force the browser to reload cached CSS and JavaScript files. Is any finite-dimensional algebra a sub-algebra of a finite-group algebra? But then I need to store either the last used ETag or the last modified to a file somewhere. #4 [1/3] FROM docker.io/library/ubuntu:18.04@sha256:05a58ded9a2c792598e8f4a #8 importing cache manifest from ######################## #8 ERROR: ##################### not found, #4 resolve docker.io/library/ubuntu:18.04@sha256:05a58ded9a2c792598e8f4aa8ffe300318eac6f294bf4f49a7abae7544918592 done, #4 sha256:3baa9cb2483bd9c5329a44d9c2fe72535625bbd4308bca95785dd58e72c06365 35.36kB / 35.36kB 0.1s done, #4 sha256:94e5ff4c0b1526abf77c236655f21c8f67a23313291c8b970fe6b469549d8153 848B / 848B 0.1s done, #4 sha256:05a58ded9a2c792598e8f4aa8ffe300318eac6f294bf4f49a7abae7544918592 1.42kB / 1.42kB done, #4 sha256:d1bf40f712c466317f5e06d38b3e7e4c98fef1229872bf6e2a8d1e01836c7ec4 1.15kB / 1.15kB done, #4 sha256:6526a1858e5d72cdffdcb41874f5f7ab3e7d531836a45bb144bf650b7242ce20 3.41kB / 3.41kB done, #4 sha256:f08d8e2a3ba11bea23cf5c17e8e1c620057412ed05c32d1114640e18d6dd0a43 747.03kB / 26.70MB 0.1s, #4 sha256:1860925334f940c3145808527480b4f0cba7f01279087fdb27679e4354fba967 163B / 163B 0.1s done, #4 sha256:f08d8e2a3ba11bea23cf5c17e8e1c620057412ed05c32d1114640e18d6dd0a43 11.64MB / 26.70MB 0.2s, #4 sha256:f08d8e2a3ba11bea23cf5c17e8e1c620057412ed05c32d1114640e18d6dd0a43 22.12MB / 26.70MB 0.3s, #4 sha256:f08d8e2a3ba11bea23cf5c17e8e1c620057412ed05c32d1114640e18d6dd0a43 26.70MB / 26.70MB 0.4s done, #4 extracting sha256:f08d8e2a3ba11bea23cf5c17e8e1c620057412ed05c32d1114640e18d6dd0a43, #4 extracting sha256:f08d8e2a3ba11bea23cf5c17e8e1c620057412ed05c32d1114640e18d6dd0a43 0.8s done, #4 extracting sha256:3baa9cb2483bd9c5329a44d9c2fe72535625bbd4308bca95785dd58e72c06365 done, #4 extracting sha256:94e5ff4c0b1526abf77c236655f21c8f67a23313291c8b970fe6b469549d8153, #4 extracting sha256:94e5ff4c0b1526abf77c236655f21c8f67a23313291c8b970fe6b469549d8153 done, #4 extracting sha256:1860925334f940c3145808527480b4f0cba7f01279087fdb27679e4354fba967 done, #9 writing image sha256:3de48a4fa457f872d7bd749e6717bd559e5a2cc4a5b15a860e1f6fa580c01c53 done, #9 naming to #############################, #10 preparing build cache for export done, > importing cache manifest from #############################, The push refers to repository [#############################], ci: digest: sha256:38421d04bbc7c69f7495c053fa424a3d2263403c1259aefea50fd90ea348284b size: 1565. @soichih, @thaJeztah, Thank you so much I found this by Googling "docker build expire cache" and I only wanted to expire a specific hash. Recent docker version? Already on GitHub? Docker picks up the change and invalidates the cache layer, nothing surprising here. It "is/was" crazy that he did not attend school for a whole month. During local builds, there is no need for a remote or persistent caching solution. ", #2 [internal] load build definition from Dockerfile, #3 [internal] load metadata for docker.io/library/ubuntu:18.04. or did you create a separate request to track this ? Sign up for a free GitHub account to open an issue and contact its maintainers and the community. Drivetrain 1x12 or 2x10 for my MTB use case? Well occasionally send you account related emails. I don't think it will be possible to only rebuild step 80, because steps 81..100 will build upon that. These secondary nodes sit doing nothing overnight so we thought it would be a good idea to scale them down in the evening and then back up in the morning so we can use the money weve saved to run more secondaries during the day when theyre in demand. Thank you. Find centralized, trusted content and collaborate around the technologies you use most. How to copy files from host to Docker container? Read more about Optimizing Your Build To Use The Docker Image Cache. Since the build stage layers are untagged and not associated with the final image, they are not part of the cached image. Asking for help, clarification, or responding to other answers. Connect and share knowledge within a single location that is structured and easy to search. to your account. Making statements based on opinion; back them up with references or personal experience. To subscribe to this RSS feed, copy and paste this URL into your RSS reader. executing a download shell script in the RUN statement instead. Some digging around revealed that Docker also uses the mtime value on a file when considering if it has changed or not. use a specific commit. I know that some dirty tricks could help e.g. In bash: And does Docker use the cache we created with the earlier docker buildfor the file? Can You Help Identify This Tool? How to mount host volumes into docker containers in Dockerfile during build. I am experiencing what I feel is inconsistent behavior using the remote docker build cache pattern in Gitlab CI. How can I prevent a Dockerfile instruction from being cached? Any RUN commands which are dependent on files whose contents frequently change should be moved to the bottom of the file. Assuming It's 1800s! That's quite a lot, it might be an idea to group them together in logical groups; Also, you can specify multiple instructions per RUN line, just as you would in the shell, e.g. For example, in your Dockerfile, put. My coding journey: To do this week = build a To Do List! This allowed me to add a mere 3 seconds to my 4 second build time rather than the full 8 minutes required to build with no cache. The tl;dr is that the remote docker cache appears to be invalidated in a situation which it should not be. To use caching on a particular service, you must add a cached declaration to your services description: Once your cache is working, you should see something like this in your build logs: Note that it will take at least two builds in order for the cached image assets to be created and used. See a detailed discussion on Issue 22832. docker build --no-cache would invalidate the cache for all the commands. With timestamp we can be 100% rest assured that the value will always be unique, besides the timestamp information can be handy if it's going to be used somewhere in the container. So if the file added has changed, the cache should be invalidated for the ADD command. By adding ONLY the Gemfile and Gemfile.lock first, and running a bundle install, the image cache for the bundle install remains valid regardless of any changes across the entire project unless the Gemfile.lock itself is changed. A decent random generator should never yield collisions (within the lifespan of the universe), and has an arbitrarily high change frequency. I didn't want to do docker build --no-cache just because I changed one line in my github project. by using HTTP ETags or by querying the last modified header field. How to get a Docker container's IP address from the host. This basically involves doing a git checkout of the branch (into existing workspaces on the primary node so we dont have to do a full initial checkout), building a Docker image that contains all of the dependencies and the version of the codebase at the time the job was ran and then running the tests inside the resulting container (on any of our secondary nodes so we can run lots of jobs in parallel, files are transferred between nodes using Jenkins stashes). The nightly image is built as a Jenkins job every night at 2am and cron jobs on the sidekicks as well as autoscaling operations ensure they have the latest nightly image every day. This was slightly confusing because I thought that Docker only invalidated the cache at a COPY line if the file had changed and it hadnt. I got the explanation of why I actually needed to expire subsequent hashes and a perfect example of how to do it. this is especially helpful for places where network download is slow (like my region). Note that branch-cache images are automatically removed after 90 days of inactivity. By default, if we cant find a cached image for the branch your current build is running on, we will fallback and look for a cached image for the master branch. This triggers a full re-build, which has a big impact on our development speed. This tutorial describes the way caching works on CodeShips infrastructure during a build. - is or was? What does the Ariane 5 rocket use to turn? Since Docker checks the files that are being COPY'ed for changes, this is what I'm using - Haven't tested it, but worth a try. Meaning of 'glass that's with canary lined'? I am wondering whether there is some more clean and native Docker functionality that I could use, here. Running on runner-############ via ip-####### 64e30c7..3cef1c0 ci -> origin/ci, #1 [internal] load build definition from Dockerfile, #5 importing cache manifest from #####################3, #6 pulling sha256:f08d8e2a3ba11bea23cf5c17e8e1c620057412ed05c32d1114640e18d6dd0a43, #6 pulling sha256:3baa9cb2483bd9c5329a44d9c2fe72535625bbd4308bca95785dd58e72c06365, #6 pulling sha256:94e5ff4c0b1526abf77c236655f21c8f67a23313291c8b970fe6b469549d8153, #6 pulling sha256:3baa9cb2483bd9c5329a44d9c2fe72535625bbd4308bca95785dd58e72c06365 0.2s done, #6 pulling sha256:1860925334f940c3145808527480b4f0cba7f01279087fdb27679e4354fba967, #6 pulling sha256:94e5ff4c0b1526abf77c236655f21c8f67a23313291c8b970fe6b469549d8153 0.2s done, #6 pulling sha256:1860925334f940c3145808527480b4f0cba7f01279087fdb27679e4354fba967 0.1s done, #6 pulling sha256:4f4fb700ef54461cfa02571ae0db9a0dc1e0cdb5577484a6d75e68dc38e8acc1, #6 pulling sha256:f08d8e2a3ba11bea23cf5c17e8e1c620057412ed05c32d1114640e18d6dd0a43 0.4s done, #6 pulling sha256:4f4fb700ef54461cfa02571ae0db9a0dc1e0cdb5577484a6d75e68dc38e8acc1 0.1s done, #9 writing image sha256:19349817088abc5038e4d23eb2e0554db9a008884935599e7a45292364e7d16b done, The push refers to repository [###################], ci: digest: sha256:4a3d8f29a086423b3ad22a3f001eafbe5ae979f3a4b9cfb352ac7ff3db0136bd size: 1565. 468), Monitoring data quality with Bigeye(Ep. You can see an example here. The best, of course, is the timestamp. In "docker time", that seems so long ago. Make sure the value is a string without any spaces, otherwise docker client will falsely take it as multiple arguments. Right now there's not a good way of reseting the cache, so it tries the command again. A great example of this doing a bundle install for a Ruby app. I took the 80/100 steps literally, because, well, you never know what somebody is trying to achieve . Dockerfile ADD command used to have the cache invalidated. I'm not familiar but sounds like just delete a portion in the local cache. Add a Dockerfile with the following contents: Confirm that the build completes successfully in CI and inspect the build logs, since it is the first build you should see, Inspect the build logs, you should see the, Make another change to the code, commit and push, Repeat as desired to observe cyclical behavior. By clicking Post Your Answer, you agree to our terms of service, privacy policy and cookie policy. This failed, during the first run of the Jenkins job the cache was invalidated at the first COPY step when we copy over the config files even though the contents of them hadnt changed. This is considered a feature https://github.com/moby/moby/issues/20316. To learn more, see our tips on writing great answers. If build speed AND small images are both critical for your application, you may choose to create a separate service in your codeship-services.yml file and cache that service, using a primary service to build and test your code and a secondary service - with a multi-stage Dockerfile - to produce your production image. Math Proofs - why are they important and how are they useful? add && exit 0 after a command will invalidate the cache from there. It falls back to sorting by highest score if no posts are trending. (To the extent that they can exist in JavaScript). @crosbymichael --no-cache is perfect! Rely on the local Docker image cache. #5 [1/3] FROM docker.io/library/ubuntu:18.04@sha256:05a58ded9a2c792598e8f4a #4 importing cache manifest from #####################, #5 resolve docker.io/library/ubuntu:18.04@sha256:05a58ded9a2c792598e8f4aa8ffe300318eac6f294bf4f49a7abae7544918592 done, #5 sha256:3baa9cb2483bd9c5329a44d9c2fe72535625bbd4308bca95785dd58e72c06365 0B / 35.36kB 0.1s, #5 sha256:94e5ff4c0b1526abf77c236655f21c8f67a23313291c8b970fe6b469549d8153 848B / 848B 0.1s done, #5 sha256:1860925334f940c3145808527480b4f0cba7f01279087fdb27679e4354fba967 0B / 163B 0.1s, #5 sha256:05a58ded9a2c792598e8f4aa8ffe300318eac6f294bf4f49a7abae7544918592 1.42kB / 1.42kB done, #5 sha256:d1bf40f712c466317f5e06d38b3e7e4c98fef1229872bf6e2a8d1e01836c7ec4 1.15kB / 1.15kB done, #5 sha256:6526a1858e5d72cdffdcb41874f5f7ab3e7d531836a45bb144bf650b7242ce20 3.41kB / 3.41kB done, #5 sha256:f08d8e2a3ba11bea23cf5c17e8e1c620057412ed05c32d1114640e18d6dd0a43 0B / 26.70MB 0.1s, #5 sha256:3baa9cb2483bd9c5329a44d9c2fe72535625bbd4308bca95785dd58e72c06365 35.36kB / 35.36kB 0.2s done, #5 sha256:1860925334f940c3145808527480b4f0cba7f01279087fdb27679e4354fba967 163B / 163B 0.1s done, #5 sha256:f08d8e2a3ba11bea23cf5c17e8e1c620057412ed05c32d1114640e18d6dd0a43 12.01MB / 26.70MB 0.4s, #5 sha256:f08d8e2a3ba11bea23cf5c17e8e1c620057412ed05c32d1114640e18d6dd0a43 19.35MB / 26.70MB 0.5s, #5 sha256:f08d8e2a3ba11bea23cf5c17e8e1c620057412ed05c32d1114640e18d6dd0a43 26.70MB / 26.70MB 0.7s, #5 sha256:f08d8e2a3ba11bea23cf5c17e8e1c620057412ed05c32d1114640e18d6dd0a43 26.70MB / 26.70MB 0.7s done, #5 extracting sha256:f08d8e2a3ba11bea23cf5c17e8e1c620057412ed05c32d1114640e18d6dd0a43 0.1s, #5 extracting sha256:f08d8e2a3ba11bea23cf5c17e8e1c620057412ed05c32d1114640e18d6dd0a43 0.8s done, #5 extracting sha256:3baa9cb2483bd9c5329a44d9c2fe72535625bbd4308bca95785dd58e72c06365 done, #5 extracting sha256:94e5ff4c0b1526abf77c236655f21c8f67a23313291c8b970fe6b469549d8153 done, #5 extracting sha256:1860925334f940c3145808527480b4f0cba7f01279087fdb27679e4354fba967 done, #9 writing image sha256:809be1b2979a2c1485d90e6d7d4cd616b240c61f80f42b2071011cea4fdbd550 done, The push refers to repository [#####################], ci: digest: sha256:1d473fa33f744301ec85c01de4b2f9659826dd87cbc9ca1445fcb9368d1b6e95 size: 1565. vagrant@vagrant-ubuntu-trusty-64:~/git/test$ sudo docker build . How to copy Docker images from one host to another without using a repository. Is there a way to remove only the specific cache? For local builds using the jet CLI, rely on the local Docker image cache. Instead, rely on the local Docker image cache for image caching during local builds. A change of a cache will invalidate all the subsequent cache layers. The docker cache is used only, and only if none of his ancestor has changed (this behavior makes sense, as the next command will add change to the previous layer). This failed because Docker wont use images pulled from a registry as part of the build cache. The cache is used if there isn't any character which has changed (so even a space is enough to invalidate a cache). Thank you for building --no-cache @crosbymichael. Question: How can I disable caching for that instructions? So it looks like Docker will re-run the step (and all the steps below it) if the string I am passing to RUN command changes in anyway - even it's just a comment. San Francisco? Where developers & technologists share private knowledge with coworkers, Reach developers & technologists worldwide. In my Dockerfile I use curl or ADD to download the latest version of an archive like: The RUN statement that uses curl or ADD creates its own image layer. This way the image cache for these steps will not be invalidated when an added file is changed. Attempt #2 was to replace pulling the Docker image, with cloning of our repository into /tmp and then building the Docker image from that version of the codebase when the node first comes up. We have a fairly standard Jenkins setup, a primary node and a whole bunch of secondaries that most of the job steps get farmed out to. vagrant@vagrant-ubuntu-trusty-64:~$ echo 'hello' > test, vagrant@vagrant-ubuntu-trusty-64:~$ mkdir git. Oh, I actually don't have any Dockerfile that has 100 steps in it (at least not yet..) I used "80 out of 100 steps" to illustrate that if I do have such Dockerfile, it will be important to be able to rebuild only the portion of the build. This way I only need to change the Dockerfile to move the COPY if I want to uncache a different stage. So we have a nightly build from a Dockerfile that looks like: With our Jenkins job now using a Dockerfile that looks like: Now all the expensive commands that we wanted cached (initial bash commands and pip installs) are in the nightly image which we pull to an instance when its created and Jenkins uses it in the FROMline. Configure a credential helper to remove this warning. Just tried with Docker version 1.12.0-rc2, it's not working, still cache the instruction. Force clean build of an image (without cache). External hard drive not working after unplugging while Windows Explorer wasn't responding.

Bullboxer Puppies For Sale Near Me, Female American Akita Temperament, Docker Cache-from Example, Newfoundland Labrador Mix, Hokkaido Deciduous Forest, Spring Boot Hello World Docker Image, German Shepherd Dog Show 2022, Shih Tzu Rescue Birmingham Al, Fluffy French Bulldog For Sale Nyc,