{"id":1846,"date":"2025-07-16T15:27:03","date_gmt":"2025-07-16T12:27:03","guid":{"rendered":"https:\/\/upcloud.com\/global\/us\/resources\/tutorials\/docker-offload-cloud-develop-local\/"},"modified":"2025-07-16T15:27:03","modified_gmt":"2025-07-16T12:27:03","slug":"docker-offload-cloud-develop-local","status":"publish","type":"tutorial","link":"https:\/\/upcloud.com\/global\/resources\/tutorials\/docker-offload-cloud-develop-local\/","title":{"rendered":"Docker Offload \u2013 Using the power of the cloud to develop locally"},"content":{"rendered":"\n

As Docker Captain, I have the privilege of testing the solutions before the public availability of the service or feature. This time, Docker prepared a few huge changes to the product, which made the whole development lifecycle much easier.<\/p>\n\n\n\n

The WeAreDeveloper announcement<\/h1>\n\n\n\n

During the keynote of WeAreDevelopers conference, Docker announced three features to the Docker Desktop, two related to AI, and one related to overall way of work.<\/p>\n\n\n\n

In this article, we dig into the general improvement of our work, Docker Offload.<\/p>\n\n\n\n

Why is it important to you?<\/h1>\n\n\n\n

Docker Offload offers functionalities that connect local development with cloud resources. For individuals and companies, the cost of modern GPU chips, cards, and computers (in general, modern GPU-powered compute power) is still expensive. Docker allows users to \u201cdelegate\u201d their local work to the cloud, where powerful GPU chips are hosted.<\/p>\n\n\n\n

At UpCloud we allow you to use very modern and powerful GPU powered units with Nvidia L40S. Unformtunatelly, Docker Offload works in Docker Cloud only, but you can run your GPU heavy tasks using docker Compose at UpCloud anyway!<\/mark><\/em><\/p>\n\n\n\n

The huge improvement for daily work is that you can more flexibly use GPUs, in on-demand and pay-as-you-go schema. <\/p>\n\n\n\n

What is Docker Offload?<\/h1>\n\n\n\n

Docker Offload allows you to move your local workloads to the Docker Cloud. What is most important here is that you don\u2019t \u201cfeel\u201d any difference in the way you work. The same CLI commands, the same system\u2019s behaviour, the same operations. The only difference is that you use Cloud-base resources, which are much more powerful than in your laptop.<\/p>\n\n\n\n

Enable Docker Offload<\/h1>\n\n\n\n

Docker Offload is part of Docker Desktop. It can be enabled from the GUI or the CLI. First, ensure you have the most recent Docker Desktop installed. If so, run the command<\/p>\n\n\n\n

docker offload start<\/code><\/code><\/pre>\n\n\n\n
You should see this screen<\/p>\n\n\n\n
\"-\"<\/figure>\n\n\n\n
On this screen, you have to select the account you want to use. In other words, you create (or select) another workspace, and after offload is enabled, you work solely there.<\/p>\n\n\n\n
The next step is to answer the GPU question.<\/p>\n\n\n\n
\"-\"<\/figure>\n\n\n\n
After confirming your selection, you are ready to go!<\/p>\n\n\n\n
\"-\"<\/figure>\n\n\n\n
The new context is ready to be used.<\/p>\n\n\n\n
The work experience<\/h1>\n\n\n\n
From the perspective of someone using Docker in CLI or Docker Desktop, nothing will change. The only difference is that everything you do, you do in the cloud. Pulling images, building, running containers, running Compose, managing containers \u2013 everything happens in the cloud, and nothing will be stored on your machine locally. Of course, your code, Dockerfiles, Compose files, etc., are still local, everything related to running your workloads goes to the cloud.<\/p>\n\n\n\n
Current pricing model<\/h1>\n\n\n\n
Docker also announced the pricing of this service. Today, we can use Docker Offload for free for 300 minutes. After that time, the price depends on the use of GPUs:<\/p>\n\n\n\n
    \n
  • $0.015 per minute if using a GPU<\/li>\n\n\n\n
  • $0.01 per minute if a GPU is not used<\/li>\n<\/ul>\n\n\n\n
    Let\u2019s run a simple test!<\/h1>\n\n\n\n
    Now that we know what Docker Offload is, how much it costs, and why you should take a look at it. It is time to see how it can be used.<\/p>\n\n\n\n
    The goal<\/h3>\n\n\n\n
    The goal of this experiment is to see if we really use cloud-based infrastructure. For this, we will check the GPU installed in the hardware we use. We will compare the local run with the offloaded run.<\/p>\n\n\n\n
    Check local hardware<\/h3>\n\n\n\n
    First, let\u2019s check the status of the Offload service, using<\/p>\n\n\n\n
    docker offload status<\/code><\/code><\/pre>\n\n\n\n
    This is what you should see<\/p>\n\n\n\n
    \"-\"<\/figure>\n\n\n\n
    Docker Offload is stopped, which means we use our local hardware. To check what GPU you have installed, run this container:<\/p>\n\n\n\n
    docker run --rm --gpus all nvidia\/cuda:12.4.0-runtime-ubuntu22.04 nvidia-smi<\/code><\/code><\/pre>\n\n\n\n
    This runs a nvidia\/cuda image, with the \u201cnvidia-smi<\/strong>\u201d command, which will provide information about the GPU chip. Also worth noting is the use of the \u201c–gpus all<\/strong>\u201d parameter.<\/p>\n\n\n\n
    When you run the container for the first time, the huge image must be pulled. It will take a moment, as the image is 2.3GB. When it is finally run, you will see something similar to my output<\/p>\n\n\n\n
    \"-\"<\/figure>\n\n\n\n
    In my case, the GPU is Nvidia GeForce GTX 1660 Ti. Yours will be different (if any).<\/p>\n\n\n\n
    Run the check in the cloud<\/h3>\n\n\n\n
    It is time to enable Offload again and check the status.<\/p>\n\n\n\n
    docker offload start<\/code><\/code><\/pre>\n\n\n\n
    docker offload status<\/code><\/code><\/pre>\n\n\n\n
    \"-\"<\/figure>\n\n\n\n
    As everything works, we can run the same container again:<\/p>\n\n\n\n
    docker run --rm --gpus all nvidia\/cuda:12.4.0-runtime-ubuntu22.04 nvidia-smi<\/code><\/code><\/pre>\n\n\n\n
    First of all, you\u2019ll see that the image is pulled. However, this time it is pulled in the cloud, in your cloud\u2019s context. And you probably noticed that the pull was quicker than in your local laptop (if not, I am jealous!).<\/p>\n\n\n\n
    What is the result?<\/p>\n\n\n\n
    \"-\"<\/figure>\n\n\n\n
    This time, the GPU chip is Nvidia L4. This confirms that we used the cloud infrastructure.<\/p>\n\n\n\n
    What can you do with Docker Offload?<\/h1>\n\n\n\n
    You can do everything you have done so far locally, but with more resources, power, and better performance. You can run Docker Compose in the same way you did before, just by using the docker compose up command. <\/p>\n\n\n\n
    As I said, the feel of use is exactly the same as for your local containers; I didn\u2019t exaggerate. When you expose a port, like 3000, for your web app, you put in your browser localhost:3000,<\/strong> and you can check this app, just as you do now. Yes, you still put localhost in your browser, even if the workload exists in the cloud.<\/p>\n\n\n\n
    How to check what context I use?<\/h1>\n\n\n\n
    There are a couple of ways to know that. First, you can run the command I already provided – <\/p>\n\n\n\n
    docker offload status<\/code><\/code><\/pre>\n\n\n\n
    Another command is<\/p>\n\n\n\n
    docker context ls<\/code><\/code><\/pre>\n\n\n\n
    Which will print the following information<\/p>\n\n\n\n
    \"-\"<\/figure>\n\n\n\n
    You can see the asterisk next to the currently selected context.<\/p>\n\n\n\n
    In Docker Desktop, there are indicators that provide this information. Like, for example, the top bar change:<\/p>\n\n\n\n
    \"-\"<\/figure>\n\n\n\n
    The picture above shows how the bar looks when you operate locally, and the picture below shows how it looks when you are using the cloud.<\/p>\n\n\n\n
    \"-\"<\/figure>\n\n\n\n
    Summary<\/h1>\n\n\n\n
    In this article, we introduced Docker Offload, a significant new feature for Docker Desktop that enables developers to run their Docker workloads in the cloud rather than solely on local machines. This is particularly advantageous for workloads demanding substantial GPU resources. <\/p>\n\n\n\n
    Developers can continue to use familiar CLI commands and experience the same operational feel, with the key difference being that all actions are executed in the cloud. <\/p>\n\n\n\n
    Key Takeaways<\/h3>\n\n\n\n
      \n
    • Cost-Effective GPU Access<\/strong>: Docker Offload provides an affordable, on-demand solution for accessing high-performance GPU compute power, eliminating the need for expensive local hardware investments.<\/li>\n\n\n\n
    • Seamless Cloud Integration<\/strong>: Developers can leverage powerful cloud resources without altering their current Docker workflows or command-line habits, ensuring a smooth transition.<\/li>\n\n\n\n
    • Enhanced Performance<\/strong>: Offloading resource-intensive operations to the cloud can significantly accelerate image pulls, builds, and container execution.<\/li>\n\n\n\n
    • Flexible Resource Utilization<\/strong>: The pay-as-you-go model allows for efficient and flexible use of cloud GPUs only when they are specifically required.<\/li>\n\n\n\n
    • Continued `localhost` Accessibility<\/strong>: Even when workloads are executed in the cloud, exposed container ports remain accessible via `localhost` in your web browser, maintaining a familiar development experience and making the development process just as easy but more powerful for developers.<\/li>\n<\/ul>\n","protected":false},"author":100,"featured_media":0,"comment_status":"open","ping_status":"closed","template":"","community-category":[241,223],"class_list":["post-1846","tutorial","type-tutorial","status-publish","hentry"],"acf":[],"_links":{"self":[{"href":"https:\/\/upcloud.com\/global\/wp-json\/wp\/v2\/tutorial\/1846","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/upcloud.com\/global\/wp-json\/wp\/v2\/tutorial"}],"about":[{"href":"https:\/\/upcloud.com\/global\/wp-json\/wp\/v2\/types\/tutorial"}],"author":[{"embeddable":true,"href":"https:\/\/upcloud.com\/global\/wp-json\/wp\/v2\/users\/100"}],"replies":[{"embeddable":true,"href":"https:\/\/upcloud.com\/global\/wp-json\/wp\/v2\/comments?post=1846"}],"version-history":[{"count":0,"href":"https:\/\/upcloud.com\/global\/wp-json\/wp\/v2\/tutorial\/1846\/revisions"}],"wp:attachment":[{"href":"https:\/\/upcloud.com\/global\/wp-json\/wp\/v2\/media?parent=1846"}],"wp:term":[{"taxonomy":"community-category","embeddable":true,"href":"https:\/\/upcloud.com\/global\/wp-json\/wp\/v2\/community-category?post=1846"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}