Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bitnami Lamp] How to locate full bitnami lamp image version from command line #1769

Open
tacoma50 opened this issue Jan 28, 2025 · 6 comments
Assignees
Labels
how-to How to issues reported by users lamp/mamp/wamp/xampp stale 15 days without activity triage Triage is needed

Comments

@tacoma50
Copy link

tacoma50 commented Jan 28, 2025

I can fine the base bitnami image version from the linux command line like this:

root@lamp-test-vm:/opt/bitnami# cat /opt/bitnami/properties.ini
[General]
base_stack_key=lampstack
base_stack_name=Bitnami package for LAMP
base_stack_version=8.2.25
installdir=/opt/bitnami

  1. But how do I find the full release version such as bitnami-lampstack-8-2-25-r3-debian-12-amd64 from the command line?

  2. Also, In Google cloud platform, is there a way to launch a specific version of the Bitnami LAMP solution?

@tacoma50 tacoma50 added the how-to How to issues reported by users label Jan 28, 2025
@github-actions github-actions bot added the triage Triage is needed label Jan 28, 2025
@gongomgra
Copy link
Collaborator

Hi @tacoma50,

Google Marketplace only allows offering one version of a given product at a time, so it is not possible to launch previous versions. Regarding how to get the full image name of a given instance programmatically, you can either use the gcloud CLI, or run the next command directly from the instance SSH console

curl -s "http://metadata.google.internal/computeMetadata/v1/instance/image" -H "Metadata-Flavor: Google" | cut -d'/' -f 5

This is the result I'm getting from a fresh server I have just started

$ curl -s "http://metadata.google.internal/computeMetadata/v1/instance/image" -H "Metadata-Flavor: Google" | cut -d'/' -f 5
bitnami-lampstack-8-4-3-r3-debian-12-amd64

You can find more information on this in the official Google docs at https://cloud.google.com/compute/docs/metadata/querying-metadata

@tacoma50
Copy link
Author

OK so that curl cmd works for my test-vm server, see output here:
test-vm:$ curl -s "http://metadata.google.internal/computeMetadata/v1/instance/image" -H "Metadata-Flavor: Google" | cut -d'/' -f 5
bitnami-lampstack-8-2-25-r1-debian-12-amd64

But I have another bitnami-lamp server called test2 that was not created from a google marketplace deployment, but it is was created from a machine image of the server test-vm above. When I run that cmd above, there is no output, as seen here:

test2:$ curl -s "http://metadata.google.internal/computeMetadata/v1/instance/image" -H "Metadata-Flavor: Google" | cut -d'/' -f 5
test2:~$

That is the problem. For test-vm I can find the bitnami version from my google cloud dashboard, when I look at ComputeEngine VMs and look at the test-vm BOOT DISK image.
But when I look at ComputeEngine VMs and look at the test2 BOOT DISK image, it's blank.

@gongomgra
Copy link
Collaborator

I'm afraid we don't save that information into our images, but you can save it on first run if you need to (either in the properties.ini file or anywhere else you prefer to), so it would get propagated to your future instances generated from that initial instance. Alternatively you can check with Google support team if there is any other key with that information in their metadata API for cloned instances.

@tacoma50
Copy link
Author

Great idea...thanks!

When you say put the bitnami version in in the properties.ini file, do you mean this file:
/opt/bitnami/properties.ini
if yes, would it be OK to add this line to the file:
base_stack_full_version=8-2-25-r3-debian-12-amd64

Will this new entry cause any issues anywhere?

Maybe you could consider adding this on future releases.

@gongomgra
Copy link
Collaborator

I think you can add your own section at the end of the ini file to avoid conflicts with current settings (just in case).

[tacoma]
base_stack_full_version=8-2-25-r3-debian-12-amd64

Thanks for the suggestion. At this moment we do not have any plan on adding more information to the properties.ini file, but we will evaluate it for the future.

Copy link

This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.

@github-actions github-actions bot added the stale 15 days without activity label Feb 19, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
how-to How to issues reported by users lamp/mamp/wamp/xampp stale 15 days without activity triage Triage is needed
Projects
None yet
Development

No branches or pull requests

2 participants