starred/netboot.xyz

Fork 0

mirror of https://github.com/netbootxyz/netboot.xyz.git synced 2026-04-26 07:35:57 +03:00

[GH-ISSUE #1607] really annoyed at lack of docker perssistant storage for images #2074

New issue

Closed

opened 2026-03-01 18:38:18 +03:00 by kerem · 8 comments

kerem commented

2026-03-01 18:38:18 +03:00

Owner

Originally created by @geekmoto13 on GitHub (Apr 8, 2025).
Original GitHub issue: https://github.com/netbootxyz/netboot.xyz/issues/1607

Is your feature request related to a problem? Please describe.
im frustrated when i have to recreate the container and redownload all the images which makes me hit my isp data cap

Describe the solution you'd like
a built in docker persistant storage for the images

Describe alternatives you've considered
no instructions currently exist on how to do this yourself on self hosting

Additional context
lab dash has been able to persist its settings and data even when updating to a new version something similar might work here

Originally created by @geekmoto13 on GitHub (Apr 8, 2025). Original GitHub issue: https://github.com/netbootxyz/netboot.xyz/issues/1607 **Is your feature request related to a problem? Please describe.** im frustrated when i have to recreate the container and redownload all the images which makes me hit my isp data cap **Describe the solution you'd like** a built in docker persistant storage for the images **Describe alternatives you've considered** no instructions currently exist on how to do this yourself on self hosting **Additional context** lab dash has been able to persist its settings and data even when updating to a new version something similar might work here

kerem

2026-03-01 18:38:18 +03:00

closed this issue
added the
enhancement
label

kerem commented

2026-03-01 18:38:19 +03:00

Author

Owner

@jkoelker commented on GitHub (Apr 8, 2025):

You should use --volume to mount in a persistent volume with docker/podman. Using the VOLUME instruction in a container file is generally frowned upon, as there is no way to disable it, you can only ever bind mount on top of it.

@jkoelker commented on GitHub (Apr 8, 2025): You should use `--volume` to mount in a persistent volume with docker/podman. Using the `VOLUME` instruction in a container file is generally frowned upon, as there is no way to disable it, you can only ever bind mount on top of it.

kerem commented

2026-03-01 18:38:19 +03:00

Author

Owner

@geekmoto13 commented on GitHub (Apr 8, 2025):

but what path to use it just has the config line in the docker config but no suggestion on what to use

/path/to/assets:/assets # optional

@geekmoto13 commented on GitHub (Apr 8, 2025): but what path to use it just has the config line in the docker config but no suggestion on what to use ``` /path/to/assets:/assets # optional ```

kerem commented

2026-03-01 18:38:19 +03:00

Author

Owner

@jkoelker commented on GitHub (Apr 8, 2025):

Whatever path you want, as long as the container runtime has access to it.

@jkoelker commented on GitHub (Apr 8, 2025): Whatever path you want, as long as the container runtime has access to it.

kerem commented

2026-03-01 18:38:19 +03:00

Author

Owner

@geekmoto13 commented on GitHub (Apr 8, 2025):

that isnt helpful, a suggestion would be something like "try

docker/netboot/assets

@geekmoto13 commented on GitHub (Apr 8, 2025): that isnt helpful, a suggestion would be something like "try ``` docker/netboot/assets ```

kerem commented

2026-03-01 18:38:19 +03:00

Author

Owner

@jkoelker commented on GitHub (Apr 8, 2025):

If you have that folder created, then that would be great path to use! Unfortunately that is not in the LSB, and any suggestion made would be different for every application, some people like to centralize their volumes in /var/lib/docker/volumes others in /var/spool/volume, still others put thing in root like /docker/netboot.

I'm sorry you're new to this and having a troubling time. Everyone is on a learning journey, and this is an open source project, no one owes you any help. Perhaps tempering your tone in the initial request and replies would be would be appropriate.

You may want to send in a PR to improve the documentation to discuss the pros and cons of selecting different locations.

@jkoelker commented on GitHub (Apr 8, 2025): If you have that folder created, then that would be great path to use! Unfortunately that is not in the LSB, and any suggestion made would be different for every application, some people like to centralize their volumes in `/var/lib/docker/volumes` others in `/var/spool/volume`, still others put thing in root like `/docker/netboot`. I'm sorry you're new to this and having a troubling time. Everyone is on a learning journey, and this is an open source project, no one owes you any help. Perhaps tempering your tone in the initial request and replies would be would be appropriate. You may want to send in a PR to improve the documentation to discuss the pros and cons of selecting different locations.

kerem commented

2026-03-01 18:38:20 +03:00

Author

Owner

@geekmoto13 commented on GitHub (Apr 8, 2025):

i was just using that as an example im using it for simplicity sake with my config but something in the documentation with possible locations as examples, just kinda ticked that my container crashed earlier and had to recreate it and resetup my instance and redownload the images which is going to take at least a week to do

@geekmoto13 commented on GitHub (Apr 8, 2025): i was just using that as an example im using it for simplicity sake with my config but something in the documentation with possible locations as examples, just kinda ticked that my container crashed earlier and had to recreate it and resetup my instance and redownload the images which is going to take at least a week to do

kerem commented

2026-03-01 18:38:20 +03:00

Author

Owner

@geekmoto13 commented on GitHub (Apr 8, 2025):

the principle is saying "use whatever you want", doesnt mean anything when a person may not know where they actually can put stuff

@geekmoto13 commented on GitHub (Apr 8, 2025): the principle is saying "use whatever you want", doesnt mean anything when a person may not know where they actually can put stuff

kerem commented

2026-03-01 18:38:20 +03:00

Author

Owner

@antonym commented on GitHub (Apr 10, 2025):

If you don't specify:

  -v /local/path/to/config:/config   `# optional` \
  -v /local/path/to/assets:/assets   `# optional` \

Things will get written into the container and then dropped when you remove the container. If those are specified, they will remain when the container is removed or deleted and will be reused again as long as you re-specify the directories. They are optional because not everyone wants things written to their disk, so it's up to the user to understand what they are doing.

@antonym commented on GitHub (Apr 10, 2025): If you don't specify: ``` -v /local/path/to/config:/config `# optional` \ -v /local/path/to/assets:/assets `# optional` \ ``` Things will get written into the container and then dropped when you remove the container. If those are specified, they will remain when the container is removed or deleted and will be reused again as long as you re-specify the directories. They are optional because not everyone wants things written to their disk, so it's up to the user to understand what they are doing.

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/netboot.xyz#2074

No description provided.

Rows
Columns