# Can't see my workspace when using docker cloud plugin **URL:** \ **Category:** Ask a question\ **Created:** [June 14, 2024, 2:46pm UTC](https://community.jenkins.io/t/cant-see-my-workspace-when-using-docker-cloud-plugin/15999 "2024-06-14T14:46:55Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![jifeg10943](https://avatars.discourse-cdn.com/v4/letter/j/bbe5ce/32.png) [@jifeg10943](https://community.jenkins.io/u/jifeg10943)\ **Post date:** [June 14, 2024, 2:46pm UTC](https://community.jenkins.io/t/cant-see-my-workspace-when-using-docker-cloud-plugin/15999/1 "2024-06-14T14:46:55Z")
Jenkins setup: Jenkins version: 2.452.1, Docker plugin version: 1.6.1 Hello, everyone, we have some jobs that uses Docker cloud as our agent But we get the error at the end of the page, and it’s possible to see workspace while the job is running and files exist on the machine. How to fix that? We want to see workspace after the build Docker plugin config Remote File System Root: /mnt/jenkins Mount: type=bind,source=/mnt/jenkins/workspace,destination=/mnt/jenkins/workspace # Error: no workspace There’s no workspace for this project. Possible reasons are: 1. The project was renamed recently and no build was done under the new name. 2. The agent this project has run on for the last time was removed. 3. The workspace directory (null) is removed outside Jenkins. 4. The workspace was wiped out and no build has been done since then. Run a build to have Jenkins create a workspace. ---
**Author:** ![MarkEWaite](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/markewaite/32/20_2.png) [@MarkEWaite](https://community.jenkins.io/u/MarkEWaite)\ **Post date:** [June 14, 2024, 3:23pm UTC](https://community.jenkins.io/t/cant-see-my-workspace-when-using-docker-cloud-plugin/15999/2 "2024-06-14T15:23:24Z")
Cloud agents are intentionally ephemeral. They are created when the job needs them and are deleted when the job is done using them. If there is something that you need to persist between jobs, you can archive an artifact. A video from Darin Pope may help: [![](https://europe1.discourse-cdn.com/flex013/uploads/jenkins/original/2X/0/0621c2f6b7c9514a1380ac5454c7fb0496385f20.jpeg "Where Does Jenkins Store Archived Artifacts?") ](https://www.youtube.com/watch?v=u6LF-T-daS4) There is a Jenkins Minute video from Liam Newman that may help: [![](https://europe1.discourse-cdn.com/flex013/uploads/jenkins/original/2X/c/c3a8d888b5864ac634b41f702ecceae7bce51d77.jpeg "Jenkins Minute - Recording Test Results and Archiving Artifacts") ](https://www.youtube.com/watch?v=c9E8kGuAwLU) There is also a tutorial from LevelUp 360 that may help: [![](https://europe1.discourse-cdn.com/flex013/uploads/jenkins/original/2X/9/9fd0ea0b14329231bdf5598a9ceb86dfa7a41b25.jpeg "How to Archive Artifacts in Jenkins") ](https://www.youtube.com/watch?v=iDbx6MiexJY) ---
**Author:** ![jifeg10943](https://avatars.discourse-cdn.com/v4/letter/j/bbe5ce/32.png) [@jifeg10943](https://community.jenkins.io/u/jifeg10943)\ **Post date:** [June 14, 2024, 3:59pm UTC](https://community.jenkins.io/t/cant-see-my-workspace-when-using-docker-cloud-plugin/15999/3 "2024-06-14T15:59:33Z")
But all our workspaces are on the machine and ephemeral agents uses those files using bind (they don’t clear workspace, I can access those files if I connect to the server), isn’t it possible to jenkins look for workspace on the machine where jenkins is installed and JENKINS\_HOME located? Our approach worked before, but something happened and it doesn’t look for workspace on machine now ---
**Author:** ![MarkEWaite](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/markewaite/32/20_2.png) [@MarkEWaite](https://community.jenkins.io/u/MarkEWaite)\ **Post date:** [June 14, 2024, 4:19pm UTC](https://community.jenkins.io/t/cant-see-my-workspace-when-using-docker-cloud-plugin/15999/4 "2024-06-14T16:19:51Z")
> [@jifeg10943](#): > > isn’t it possible to jenkins look for workspace on the machine where Jenkins is installed and JENKINS\_HOME located? It might be possible, but that’s not how Jenkins treats ephemeral agents. Ephemeral agents are assumed to store their workspace on the agent. When the agent ceases to exist, the workspace is no longer assumed to be available. Your choice to run the agents on the same computer as the controller is a valid choice but it is not the only choice for Jenkins users with ephemeral agents and I suspect it is not the most common choice.