• 0 Posts
  • 9 Comments
Joined 3 years ago
cake
Cake day: June 14th, 2023

help-circle

  • If you go with dual booting this is what worked for me when I have done dual boot, so windows doesn’t mess with boot options:

    1. Window have to be installed first or already there.
    2. With a Live ISO use a tool like gparted and shrink windows main partition from the right.
    3. During installation, choose custom partitioning to manage the free space
    • Make a secondary /boot/efi partition so linux boot is installed there.
    • Make the / root partition for linux and optional make a partition for /home.
    • Finish the installation.
    1. Boot into UEFI and change boot order to that secondary /boot/efi.
    2. Reboot and profit.

    That way grub will be running from the secondary /boot/efi, and it will detect and add windows and the primary /boot/efi

    Windows only sees and care about the first /boot/efi and will only mess with that, so even if it does change something it doesn’t matter.



  • As far as I know, Dockge, Portainer, Coolify, etc. can have different stacks folders, and they will not show, warn you or not let you manage stacks outside their designated paths.

    For your main question, it is possible to build your image on the same system, you would need at least terminal access to do so, and then use the local image with docker compose or Dockge or other, you just would need to reference its image name instead of a URL (to differentiate images I build I prefix their name with local as ‘local/service-name’), and it would not pull from anywhere but use the one you already built, you could do it on any folder on the system or inside the stacks folder you have with Dockge

    If you do it on Dockge’s stack folder, create a folder for your service, with a docker-compose.yml file inside (with just this it will appear in Dockge), then pull the repository on this folder, and make sure you have the proper Dockerfile to build the image, you can then either build the image first or reference the Dockerfile on your docker-compose.yml. This way when you do docker compose up or in Dockge you press the Start button, it will build the image with the Dockerfile and use it, if it doesn’t find the image.

    The other option I know is to have a local image registry (I have done this with Forgejo), so pull the repository on any folder on your system, build it and push it to your local registry, and then just use the local registry URL on your docker-compose-yml